Issue #4408 has been updated by Henrik Lindberg. Status changed from Accepted to Duplicate
This is a duplicate of #1198. Comment 7 in this issue (4408) describes a problem that is by design - it is illegal to reference parameter values, the order of initialization is not defined. Arguably an error message to that effect should be produced instead of silent use of undefined value. That is not however what this issue is about. ---------------------------------------- Feature #4408: A 'strict' variable mode should be added https://projects.puppetlabs.com/issues/4408#change-73411 Author: Stig Sandbeck Mathisen Status: Duplicate Priority: Normal Assignee: Category: language Target version: Affected Puppet version: 0.25.1 Keywords: Branch: This is an issue reported in the Debian Bug Tracker at [[http://bugs.debian.org/563550]]. Excerpt: <blockquote> The puppet manifest language uses empty variables the same way then undefined ones. Many languages, for example perl and sql, have shown in the past that this behaviour produces hard to find errors all over the code. Example: lsb* are undefined if lsb-release is missing. A definition using this needs to explicitely check for the lack of a value. It would be obvious if it bails out on the variable access. This is also different from the behaviour of the templating language, erb bails out on undefined variables. </blockquote> -- 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.
