Jira (PUP-2160) Undocumented hash lookup change in Puppet 3.5.0

[Per Cederqvist (JIRA)]

Title: Message Title

Per Cederqvist commented on an issue   Re: Undocumented hash lookup change in Puppet 3.5.0 Thank you for your explanation. I think I understand more now, and it certainly makes sense not to document things that might change. But. I propose that a sentence similar to this is added to <http://docs.puppetlabs.com/puppet/latest/reference/lang_datatypes.html#indexing-1>: If you index a hash with a key that isn't present in the hash, the special value undef is returned. This addition should be uncontroversial, as it documents the current behaviour in Puppet 3.5.0, and if I understand you correctly there are no plans to change this particular behaviour. If I had written my code so that it checked for undef instead of checking for the empty string, it would have worked in both Puppet 3.4.3 and 3.5.0, with both the future and the current parser. Add Comment   Puppet / PUP-2160 Undocumented hash lookup change in Puppet 3.5.0 Consider this code: {noformat} $h = { "k1" => "value" } $v = $h["k2"] {noformat} Puppet 3.5.0 sets $v to undef. Earlier versions set $v to the empty string, I believe. (Possibly that isn't true. Possibly it is instead some comparison changes that bites me.) What happens when you look up a non-existing key in a hash should be documented on htt... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.