Re^2: Is { } an empty block or a bug in perl?

When you use empty hashrefs, are they by themselves, or are they at least assigned to something or used as an arguement to a subroutine? I cannot think of anytime that I've just put an empty structure dangling in the wind. If you do, could you provide an example? I'm genuinely curious.

thor

Feel the white light, the light within Be your own disciple, fan the sparks of will For all of us waiting, your kingdom will come

Comment on Re^2: Is { } an empty block or a bug in perl?

Replies are listed 'Best First'.
Re^3: Is { } an empty block or a bug in perl? by Joost (Canon) on Jul 06, 2005 at 15:59 UTC
I was thinking of things like this, where the assignment is done later: `sub gimme_my_data { my $self = shift; $self->{data} \|\| {} }` [download] you could use a code block there too if you want to ( `\|\| do { ... }`). "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply] [d/l] [select]
Re^4: Is { } an empty block or a bug in perl? by thor (Priest) on Jul 06, 2005 at 22:51 UTC
After I wrote the initial reply this morning, I was thinking that it might be this sort of thing. I like to use an explicit `return` in my subs, so I guess I wouldn't run into this problem. thor `Feel the white light, the light within Be your own disciple, fan the sparks of will For all of us waiting, your kingdom will come`	[reply]
Re^5: Is { } an empty block or a bug in perl? by Joost (Canon) on Jul 06, 2005 at 23:48 UTC
You can do the same as the last statement in an included file: `$r = do "file.pl"` [download] and in "file.pl" `{}` [download] update: by the way: whether or not you add a "return" to the last statement doesn't make any difference. It just makes it more explicit. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply] [d/l] [select]
Re^6: Is { } an empty block or a bug in perl? by thor (Priest) on Jul 07, 2005 at 02:24 UTC