Jira (PUP-523) Add 'private' as a keyword to make classes (and defines?) private to a module

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: Add 'private' as a keyword to make classes (and defines?) private to a module I don't understand the motivation to put this off until later. While the functionality comes during 4x, the keyword should be reserved in 3.7 future, and issue a deprecation warning in 3.7 current. We would otherwise have a breaking change to introduce this. This issue (PUP-523) is about adding it as a reserved keyword only. Suggested implementation is to introduce it in the lexer and grammar where it will appear, and to validate it - (decide on one of): a warning that it has no effect yet an error no-op silently ignored The "recognize and validate" provides the best possibility to provide feedback. Add Comment   Puppet / PUP-523 Add 'private' as a keyword to make classes (and defines?) private to a module Add the keyword 'private' to classes (and defines?) to make them restricted for use from within the same module. 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.