Jira (PUP-1221) Mixed invocation of parameterized classes leads to order dependencies, should be disallowed

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: Mixed invocation of parameterized classes leads to order dependencies, should be disallowed The behavior is not different in the future evaluator in 3.5 since it stops being "new" when it deals with resources, classes, relationships and queries - i.e. "catalog operations" - these are handled by the same logic as the current evaluator - it only got there in a different way. If we fix this it will (currently) be for both 3x and future. Not sure how difficult it is. We also have a strong desire to rework the entire compiler/resource layer - but it is out of scope for the 3.5 future evaluator. (There are many issues that are related to the implementation of Resource). Add Comment   Puppet / PUP-1221 Mixed invocation of parameterized classes leads to order dependencies, should be disallowed When a parameterized class has default values for all of its parameters, it may be invoked using either "include" or class \{ ... \} notation. The "include" notation is idempotent; the class \{ ... \} notation isn't. As a result, there is an order dependency. This works: {code} class foo($param = defaultvalue) {   notify { $param: } } class {... 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/groups/opt_out.