Um... they're both the wrong way to write @foo, but the second one's more inefficient, but caring excessively about efficiency of bad code that you should refactor anyway is a premature optimization, so ... umm... it's a trick question, with the answer of "There's no difference; you'ld never use either one in production code?"
Do I win? :-) Or did I miss something subtle? :-(
In reply to Re^3: What's so bad about &function(...)?
by Anonymous Monk
in thread What's so bad about &function(...)?
by japhy
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |