Issue #15329 has been updated by Henrik Lindberg.
This is on the agenda for Puppet 4 - it is a major semver breaking change. It may be available earlier in experimental feature form but is not going to make it in time for Puppet 3.4. ---------------------------------------- Bug #15329: Puppet lacks a proper "undefined" value https://projects.puppetlabs.com/issues/15329#change-99302 * Author: Pieter van de Bruggen * Status: Accepted * Priority: Normal * Assignee: Henrik Lindberg * Category: * Target version: * Affected Puppet version: * Keywords: backlog * 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
