Home > Archive > PERL Miscellaneous > July 2005 > FAQ 4.67 Why does passing a subroutine an undefined element in a hash create it?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
FAQ 4.67 Why does passing a subroutine an undefined element in a hash create it?
|
|
| PerlFAQ Server 2005-07-27, 5:05 pm |
| This message is one of several periodic postings to comp.lang.perl.misc
intended to make it easier for perl programmers to find answers to
common questions. The core of this message represents an excerpt
from the documentation provided with Perl.
--------------------------------------------------------------------
4.67: Why does passing a subroutine an undefined element in a hash create it?
If you say something like:
somefunc($hash{"nonesuch key here"});
Then that element "autovivifies"; that is, it springs into existence
whether you store something there or not. That's because functions get
scalars passed in by reference. If somefunc() modifies $_[0], it has to
be ready to write it back into the caller's version.
This has been fixed as of Perl5.004.
Normally, merely accessing a key's value for a nonexistent key does
*not* cause that key to be forever there. This is different than awk's
behavior.
--------------------------------------------------------------------
Documents such as this have been called "Answers to Frequently
Asked Questions" or FAQ for short. They represent an important
part of the Usenet tradition. They serve to reduce the volume of
redundant traffic on a news group by providing quality answers to
questions that keep coming up.
If you are some how irritated by seeing these postings you are free
to ignore them or add the sender to your killfile. If you find
errors or other problems with these postings please send corrections
or comments to the posting email address or to the maintainers as
directed in the perlfaq manual page.
Note that the FAQ text posted by this server may have been modified
from that distributed in the stable Perl release. It may have been
edited to reflect the additions, changes and corrections provided
by respondents, reviewers, and critics to previous postings of
these FAQ. Complete text of these FAQ are available on request.
The perlfaq manual page contains the following copyright notice.
AUTHOR AND COPYRIGHT
Copyright (c) 1997-2002 Tom Christiansen and Nathan
Torkington, and other contributors as noted. All rights
reserved.
This posting is provided in the hope that it will be useful but
does not represent a commitment or contract of any kind on the part
of the contributers, authors or their agents.
| |
| Paul Lalli 2005-07-27, 5:05 pm |
| PerlFAQ Server wrote:
> 4.67: Why does passing a subroutine an undefined element in a hash create it?
>
> If you say something like:
>
> somefunc($hash{"nonesuch key here"});
>
> Then that element "autovivifies"; that is, it springs into existence
> whether you store something there or not. That's because functions get
> scalars passed in by reference. If somefunc() modifies $_[0], it has to
> be ready to write it back into the caller's version.
>
> This has been fixed as of Perl5.004.
>
> Normally, merely accessing a key's value for a nonexistent key does
> *not* cause that key to be forever there. This is different than awk's
> behavior.
Er, if this was fixed a good 5 versions ago, is this FAQ really still
relevant? Are there really that many people still using anything less
than 5.004? (And if there are, and they have a problem about things
not working, shouldn't the answer be "Upgrade your Perl"?)
Paul Lalli
| |
| James Taylor 2005-07-28, 9:09 am |
| In article <1122489468.920709.91510@g43g2000cwa.googlegroups.com>,
Paul Lalli <mritty@gmail.com> wrote:
>
> PerlFAQ Server wrote:
>
> Er, if this was fixed a good 5 versions ago, is this FAQ
> really still relevant? Are there really that many people
> still using anything less than 5.004? (And if there are,
> and they have a problem about things not working,
> shouldn't the answer be "Upgrade your Perl"?)
Upgrading their Perl version may not be an option. It
certainly wouldn't be a practical option for me. Thankfully,
the RISC OS port by Nicholas Clark, is up to 5.005_03 but
there are plenty of newer Perl features that I'm stuck not
being able to use. Being unsympathetically told to upgrade
wouldn't be helpful.
I think this FAQ entry should stand as it helps anyone stuck
with an earlier version to discover the potential problem,
helps us all be more mindful of autovivification traps, and
gives people who *can* upgrade a good reason to do so.
--
James Taylor, London, UK PGP key: 3FBE1BF9
To protect against spam, the address in the "From:" header is not valid.
In any case, you should reply to the group so that everyone can benefit.
If you must send me a private email, use james at oakseed demon co uk.
|
|
|
|
|