Justin Mason <[EMAIL PROTECTED]> writes: > +1 on "1 means OK, 0/undef means error". IMO, undef is more > appropriate and perlish.
-0.9 on changing all the "return 0" statements in the code to undef, -1 without a reason. 0 means false and it is used to indicate 0 bytes, 0 offset, 0 count, etc. It sometimes has a dual context, so making every "false" an undef *will* break stuff which is hardly appropriate. undef is generally more appropriate when the return code is a byte offset, size, or something else where 0 is a possible correct response. Daniel -- Daniel Quinlan anti-spam (SpamAssassin), Linux, http://www.pathname.com/~quinlan/ and open source consulting
