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

[Charlie Sharpsteen (JIRA)]

Title: Message Title

Charlie Sharpsteen commented on an issue   Re: Undocumented hash lookup change in Puppet 3.5.0 The reported issue puzzles me a bit, there is transformation to 3x when calling a function, and IIRC it is required that undefined values are transformed to empty strings in the function API During my testing, the change seemed to be that the current evaluator stores the value of $v as :undef in the Scope @symtable}, while the future evaluator stores a nil. I'm not sure if this behavior is a result of the function API. 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.