Re^2: my behavior with "NULL" declarations

I got the same thing when using a literal. So then its something about the shift that my doesn't like. It's weird that it's like that since that's not the piece being declared. Why would my care whether or not the condition is NULL since it only one of the other two parts that get's returned by the condition? At least I think...

dsb
This is my cool %SIG

Comment on Re^2: my behavior with "NULL" declarations

Replies are listed 'Best First'.
Re^3: my behavior with "NULL" declarations by dragonchild (Archbishop) on Jul 08, 2004 at 18:18 UTC
At compile-time, the expression is NULL. At run-time, it will do stuff, but compile-time doesn't know that yet. ------ We are the carpenters and bricklayers of the Information Age. Then there are Damian modules.... sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon.* - flyingmoose I shouldn't have to say this, but any code, unless otherwise stated, is untested	[reply]

Replies are listed 'Best First'.

Re^3: my behavior with "NULL" declarations
by dragonchild (Archbishop) on Jul 08, 2004 at 18:18 UTC

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

I shouldn't have to say this, but any code, unless otherwise stated, is untested

[reply]