comment on

I'm pretty sure the answer is the same as in your previous thread that you referenced: map is providing lvalue context to its args, while the other two examples of string concatenation do not, hence the hash value is autovivified. (Update: I added LanX's suggested workaround to the following example).

$ perl -wMstrict -MData::Dump -e 'my %h; map{$_} $h{X},"$h{Y}"; dd\%h'
Use of uninitialized value $h{"Y"} in string at -e line 1.
{ X => undef }
[download]

See also your previous thread No autovivification, for loop aliasing, lvalue vs rvalue in for loops.

I'm curious why you have so many issues with autovivification? Personally, I hardly ever do, because I use exists, or keys when looping over multiple hash keys. And if I have a situation where I want to control which keys can be accessed, I use locked hashes from Hash::Util.

In reply to Re: Sometimes undef is initialized and sometimes not when hash values are fed to grep by haukex
in thread Sometimes undef is initialized and sometimes not when hash values are fed to grep by leszekdubiel

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks