Issue #8783 has been updated by Matt Robinson.
I think the way Nan wrote it is correct. If you're going to have optional variables, you're going to need logic to handle them. It might be more verbose, but it's also much clearer what's happening, and we don't need to make decisions about how nil compares to zero and empty string. This also means that people who didn't MEAN to have optional variables will find the failure sooner rather than later. ---------------------------------------- Bug #8783: Previously working equality operator case now fails on ':undef:Symbol'. https://projects.puppetlabs.com/issues/8783 Author: Trevor Vaughan Status: Needs Decision Priority: High Assignee: Nigel Kersten Category: parser Target version: Affected Puppet version: 2.6.0 Keywords: Branch: The following code worked on 0.24.X: <pre> # The variables are not defined purposefully if $foo < $bar { notify { "test": } } </pre> In the 2.6 and 2.7 series, it throws the following error: <pre> undefined method `<' for :undef:Symbol </pre> Wrapping the variables in double quotes works but it not ideal for legacy code migration. -- 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.
