Issue #15329 has been updated by eric sorenson.
I've extracted all of the use cases and test code from the bugs linked above and put them into a 'modulepath' compatible git repository: https://github.com/ahpook/puppet-undef Hopefully this will be a useful, concrete starting point as we're trying to define what behaviour we want and making sure that things are consistent for the various things people want out of the DSL. ---------------------------------------- Bug #15329: Puppet lacks a proper "undefined" value https://projects.puppetlabs.com/issues/15329#change-69626 Author: Pieter van de Bruggen Status: Accepted Priority: High Assignee: Pieter van de Bruggen Category: Target version: Affected Puppet version: Keywords: Branch: $y = undef notice($y == "") # true notice($x == $y) # true notice($x == "") # true Recent changes in the Puppet DSL made equality commutative (good!), but in doing so broke work-arounds for actually testing for the difference between an undefined and "empty" value. The most logical fix would be to equate Puppet's `undef` with Ruby's `nil`. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
