Re^4: Two simple code style advice questions

It would seem to me that most Unix commands return 0 when things are "OK." So.. if you want to accuse me of showing my C programming roots, I plead guily.

I understand the derivation, but still, the bland token OK has always suggested TRUE to me, and always will.

Hence my suggested alternative of use constant NOERROR => 0; which seems less likely to cause confusion.

That said, I wouldn't define a constant for 0 at all. It simply isn't necessary to compare against zero in Perl. The clearest idiom is simply:

my $errstr = $case ? $msg[ $case ] : '';
[download]

But I'd still prefer setting $msg[ 0 ] == ''; and simply:

my $errstr = $msg[ $case ];
[download]

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re^4: Two simple code style advice questions Select or Download Code