Re: Why use strict is good, and barewords are bad

in reply to Why use strict is good, and barewords are bad

Let's make matters worse

And let's see what we could make with all the other months :-)

jan - join, but faster
feb -
mar - (did you know "mar" is Portuguese for "sea"?)
apr - note that code is almost apt
may - may happen; like, it really doesn't matter whether the code produces an error
jun - even faster
jul - so fast that it'll suffle the elements and even lose some of them
aug - turn things into gold?
sep - make it SEP (somebody else's problem); if it catches an error, throw it to another process
oct - octal
nov -
dec - decimal

Anyone has other ideas, perhaps to complete the list? :-)

(OK, I admit it... that was really stupid...)

Comment on Re: Why use strict is good, and barewords are bad

Replies are listed 'Best First'.
Re^2: Why use strict is good, and barewords are bad by 5mi11er (Deacon) on Apr 22, 2005 at 14:19 UTC
I'd had the same thought off and on since leaving from work yesterday. You did much better than I'd been able. I was trying to use them all as TLA's, but hadn't come up with a single good one yet, but did figure I'd steal the APR idea from way up above. Just Another Nitwit Match Against Regex Pretty lame, and those are my best so far... -Scott	[reply]
Re^3: Why use strict is good, and barewords are bad by Anonymous Monk on Apr 22, 2005 at 14:58 UTC
JAN: Java Alert Notification FEB: Free Each Binary MAR: Must Always Run APR: Average Programmer Rate MAY: May Abort Yearly JUN: Jump Until Near JUL: Join Unique List AUG: Accelerate Ultimate Game SEP: Shift Extra Parameter OCT: Open, Close and Truncate NOV: Next Old Vector DEC: Do Expected Calculation	[reply]

In Section Meditations