Re^3: Tree::Nary Question

Replies are listed 'Best First'.
Re^4: Tree::Nary Question by ikegami (Patriarch) on Mar 09, 2011 at 00:19 UTC
It's good cause it catches errors, right? My point was that it's silly to say the messages that result from such errors aren't error messages.	[reply]
Re^5: Tree::Nary Question by Dandello (Monk) on Mar 09, 2011 at 02:02 UTC
Well, there are 'error' errors that stop the script - like mismatched brackets - then there are 'warning' errors that tell you something's wrong, but not bad enough to crash the program. Warnings are things you need to know about, but Perl will try to 'guess' what was meant or needed. In this case, the module needed three parameters and warned when there were only two - but it still kept going. But with the missing parameter, it couldn't give the proper result as the value it used to keep going with would have been 0 or null. So yes, it's an 'error' but a non-fatal one.	[reply]
Re^6: Tree::Nary Question by ikegami (Patriarch) on Mar 09, 2011 at 07:19 UTC
Exactly, but for some reason, people have been going out of their way to say that errors that aren't fatal aren't errors. I was just addressing an instance of this. Some errors are fatal, and some errors produces warnings. Warnings are also produced spuriously, which is an error in of itself. Saying they're not errors is just plain wrong.	[reply]
Re^7: Tree::Nary Question by Anonymous Monk on Mar 09, 2011 at 08:19 UTC
Re^6: Tree::Nary Question by ikegami (Patriarch) on Mar 09, 2011 at 07:24 UTC
Exactly, but for some reason, people have been going out of their way to say that errors that aren't fatal aren't errors. I was just addressing an instance of this. Some errors are fatal, and some errors produces warnings. Warnings are also produced spuriously, which is an error in of itself. Saying they're not errors is just plain wrong.	[reply]