"$Bill Luebkert" <[EMAIL PROTECTED]> graced perl with these words of wisdom:
>> Using that index returns >> incorrect data instead of an undefined value, which makes it much >> harder to detect that bug. Besides, what's so hard about >> saying [EMAIL PROTECTED] as opposed to $array[-1] ? > > Nothing, but there's always a trade-off between extra features and > possbile misuse of same. When you design a language, you can't > possibly think of all the misuses that can occur due to bugs. This reminds me of the old question from perlfaq4 (which may or may not be in the current FAQs for Perl): <snip> Does Perl have a Year 2000 problem? Is Perl Y2K compliant? Short answer: No, Perl does not have a Year 2000 problem. Yes, Perl is Y2K compliant (whatever that means). The programmers you've hired to use it, however, probably are not. Long answer: The question belies a true understanding of the issue. Perl is just as Y2K compliant as your pencil--no more, and no less. Can you use your pencil to write a non-Y2K-compliant memo? Of course you can. Is that the pencil's fault? Of course it isn't. [...] </snip> -- Ted <fedya at bestweb dot net> TV Announcer: It's 11:00. Do you know where your children are? Homer: I told you last night, *no*! <http://www.snpp.com/episodes/4F06.html> _______________________________________________ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
