diff options
| author | David Mitchell <davem@iabyn.com> | 2011-01-21 17:23:51 +0000 |
|---|---|---|
| committer | David Mitchell <davem@iabyn.com> | 2011-01-21 17:25:05 +0000 |
| commit | 6e4c4703d5584b6bcbb9adfe4cdff420d0c88911 (patch) | |
| tree | f66c2507e897782660d17ffa7c15481674ceed19 /pod/perldata.pod | |
| parent | da392a17e090fe9071ca559e3e917a7659baf7af (diff) | |
| download | perl-6e4c4703d5584b6bcbb9adfe4cdff420d0c88911.tar.gz | |
RT #75870 perldata.pod tied hash in scalar context
update inaccurate description.
Diffstat (limited to 'pod/perldata.pod')
| -rw-r--r-- | pod/perldata.pod | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perldata.pod b/pod/perldata.pod index 4ec9eb55a1..98663c467f 100644 --- a/pod/perldata.pod +++ b/pod/perldata.pod @@ -276,8 +276,8 @@ set. For example, you stick 10,000 things in a hash, but evaluating %HASH in scalar context reveals C<"1/16">, which means only one out of sixteen buckets has been touched, and presumably contains all 10,000 of your items. This isn't supposed to happen. If a tied hash -is evaluated in scalar context, a fatal error will result, since this -bucket usage information is currently not available for tied hashes. +is evaluated in scalar context, the C<SCALAR> method is called (with a +fallback to C<FIRSTKEY>). X<hash, scalar context> X<hash, bucket> X<bucket> You can preallocate space for a hash by assigning to the keys() function. |