On Thu, 30 Oct 2003 14:53:09 -0800, Kenneth Porter <[EMAIL PROTECTED]> posted to gmane.mail.spam.spamassassin.general: > In other code (MIMEDefang) I've seen the use of a positional > parameter list (eg. "($$$$)") on functions to ensure that enough > values are passed. Does it make sense for SA to start using this?
You can't do that with object-oriented code because the parameter list is checked at compile time and you can't know at that point what's right for a class. (Skimping over the parts I don't remember exactly -- see the Camel Book or the perltoot man page, just before SEE ALSO.) However, of course you can use something like (defined $atime ? $atime : 0) or the new fancy // operator which is going to be in a future version of Perl. <http://use.perl.org/articles/03/09/26/2231256.shtml?tid=6> Maybe. If you can come up with a test case which triggers the bug, I imagine it won't be hard to fix. /* era */ -- The email address era the contact information Just for kicks, imagine at iki dot fi is heavily link on my home page at what it's like to get spam filtered. If you <http://www.iki.fi/era/> 500 pieces of spam for want to reach me, see instead. each wanted message. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
