Re: How should I understand scalar(%hash) results?

Good guess :) From perldata:

..., but evaluating %HASH in scalar context reveals "1/16", which means only one out of sixteen buckets has been touched, ...

Examine what is said, not who speaks.

"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon

Comment on Re: How should I understand scalar(%hash) results?

Replies are listed 'Best First'.
Re^2: How should I understand scalar(%hash) results? by TVSET (Chaplain) on Oct 05, 2004 at 08:47 UTC
Oh, thanks. I guess I missed this bit somehow... Leonid Mamtchenkov aka TVSET	[reply]
Re^3: How should I understand scalar(%hash) results? by thospel (Hermit) on Oct 05, 2004 at 09:08 UTC
In normal programs the only interesting thing about this is that it's guaranteed to return false for an empty hash and something that's true otherwise. So you can check if a hash is empty or not by simply using the hash name in boolean context (which is a scalar context): `if (%hash) { ..do something for a filled %hash... } else { ...do something for an empty %hash... }` [download]	[reply] [d/l]