Issue #5027 has been updated by Nick Lewis. Status changed from Accepted to Ready for Testing Branch set to http://github.com/nicklewis/puppet/tree/feature/next/5027
Scopes now track how they acquired their parents (dynamic scope from being included vs. inheritance). This allows us to simulate static scope when looking up variables, compare it to the result of the dynamic lookup, and issue a warning if the results differ. Such a warning is only issued once per compile. ---------------------------------------- Feature #5027: Issue warnings when using dynamic scope https://projects.puppetlabs.com/issues/5027 Author: Paul Berry Status: Ready for Testing Priority: Normal Assignee: Paul Berry Category: language Target version: Statler Affected Puppet version: Keywords: Branch: http://github.com/nicklewis/puppet/tree/feature/next/5027 This ticket captures a decision made on the developer mailing list on Oct 12 (see email thread "Questions about variable scope"). In Puppet version 2.7, a deprecation warning should be issued whenever a variable reference takes place or a resource default is applied as a result of dynamic scoping. Dynamic scoping means that variables and resource defaults defined in class A also take effect in classes that A includes. The warning should advise users that this feature will be removed in a future version of Puppet, so they should start using other puppet features (such as parameterized classes) to achieve the desired effect. -- 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.
