Re^2: use Strict: a rigorous way to break my command line variables?

Oh wow. Thanks, tilly, you got it. I'm using MaxOSX though, hurumph;)

I did type "use Strict" instead of "use strict." When I change it to the lowercase version, everything works again.

Don't know why I used uppercase. Perhaps it seemed Even Stricter!

"I'm not afraid of Al Quaeda. I'm afraid of Al Cracker." -Chris Rock

Comment on Re^2: use Strict: a rigorous way to break my command line variables?

Replies are listed 'Best First'.
Re^3: use Strict: a rigorous way to break my command line variables? by tilly (Archbishop) on Aug 09, 2006 at 02:33 UTC
When I see people using a case insensitive filesystem, I just assume they are using Windows. Bad assumption. Sorry.	[reply]
Re^3: use Strict: a rigorous way to break my command line variables? by sgt (Deacon) on Aug 10, 2006 at 20:42 UTC
it's funny, on the p5p mailing list today, somebody had filed a bug concerning this exact problem; Rafael actually answered by quoting the perl source that was saying that this could not be fixed, that the previous fix was bad and had been withdrawn, and the rationale behind it. The truth is that this kind of filesystem should be fixed!	[reply]