diff options
| author | Yitzchak Scott-Thoennes <sthoenna@efn.org> | 2003-05-07 08:27:07 -0700 |
|---|---|---|
| committer | Jarkko Hietaniemi <jhi@iki.fi> | 2003-05-08 18:12:46 +0000 |
| commit | 126c71c82576d5dc652db25ca9e3f8e18442c4fd (patch) | |
| tree | e2790a78faaa94be96e8fcce8035cddddae1602e /pod/perldata.pod | |
| parent | 86e5a81e88dbe10bf1c195d6ca6fefab8bfafc17 (diff) | |
| download | perl-126c71c82576d5dc652db25ca9e3f8e18442c4fd.tar.gz | |
Re: [perl #17718] %tiedhash in bool context doesn't check if hash is empty
Message-ID: <7gYu+gzkgaFU092yn@efn.org>
p4raw-id: //depot/perl@19452
Diffstat (limited to 'pod/perldata.pod')
| -rw-r--r-- | pod/perldata.pod | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/pod/perldata.pod b/pod/perldata.pod index 572058924f..c58d41974a 100644 --- a/pod/perldata.pod +++ b/pod/perldata.pod @@ -257,7 +257,9 @@ Perl's internal hashing algorithm is performing poorly on your data 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. +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. You can preallocate space for a hash by assigning to the keys() function. This rounds up the allocated buckets to the next power of two: |