Re^2: what is bad about this?

What are you talking about?
Neither
$IP_ADDRESS = @REALM[1];
nor
$IP_ADDRESS = $REALM[1];
generates a warning.

~~And~~ strict is not relevant. If one generates a strict fault, so will the other. If one doesn't generate a strict fault, neither will the other.

Comment on Re^2: what is bad about this? Select or Download Code

Replies are listed 'Best First'.
Re^3: what is bad about this? by runrig (Abbot) on Feb 06, 2006 at 21:45 UTC
Maybe it's a new warning? (From 5.8.4): `Scalar value @REALM[1] better written as $REALM[1] at ...` [download] Also, I'm just guessing the OP is using neither strict nor warnings. If he was using warnings, he'd be getting a warning and probably fixing it, and he'd probably already be using strict. If he does start using strict and warnings, then I bet there will be a bunch of errors to fix (and a good chance that either version of that line will need to be fixed).	[reply] [d/l]
Re^4: what is bad about this? by ikegami (Patriarch) on Feb 06, 2006 at 21:47 UTC
No, my fault. The warning is present in 5.6.1. Reminder to self: Verify before contradicting someone!	[reply]