in reply to Warnings vs. Errors

Errors forcibly exit the program with a non-zero exit code (unless caught - if possible - using eval {}). Warnings don't (and can't be caught with eval {} either).

See also the difference between die and warn.

update: to check for a non-zero exit code, you can do something like this in a bash/sh type shell: 

perl some_program.pl || echo "That was an error"

[download]
update 2 please don't double post. especially not an hour after the first post.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Replies are listed 'Best First'.
Re^2: Warnings vs. Errors
by cormanaz (Deacon) on Aug 15, 2008 at 23:09 UTC
    The double post was an accident that happened because I refreshed the page that comes up after you post a post, thinking that would give me a look at any replies that had come up. Instead it made a dupe. (Why is it designed that way?)

    As soon as I realized what happened I asked on CB for someone to delete it and was told it couldn't be done.

[reply]
[reply]

In Section Seekers of Perl Wisdom