Jira (PUP-2042) Inconsistent behavior when setting one class parameter equal to another

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: Inconsistent behavior when setting one class parameter equal to another The behavior is undefined, and inconsistently implemented. The rule is - do not attempt to access other parameters in the same list. See PUP-1985 which this issue duplicates. Add Comment   Puppet / PUP-2042 Inconsistent behavior when setting one class parameter equal to another In the past (Puppet 2.7.x), you could set one class parameter equal to another, by default. E.g.: {noformat} class klass ($foo = 'value', $bar = $foo) {   notify { "Foo is ${foo}": }   notify { "Bar is ${bar}": } } include klass {noformat} In the above scenario, in Puppet 2.7.x, the values of both variables end up set as {{value}}. In P... 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.