Jira (PUP-2695) defining a class twice "merges" their behaviors

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: defining a class twice "merges" their behaviors I think we should change this for future parser in 3.7, and for real in Puppet 4.0. Also add a deprecation warning for the non future parser in 3.x. The location of the behavior is confined to Puppet::Resource::Type#merge where other issues such as checking if freeze_main is on is located. Add Comment   Puppet / PUP-2695 defining a class twice "merges" their behaviors A new hire ([~erin]) is working through exercises and inadvertently defined a class twice in a file with surprising results. {code} class test {   notice('testing')   notify { 'first': } } class test {   notice('again')   notify { 'surprise!': } } include test {code} {code} [root@student ~]# puppet apply test.pp Notice: Scope(Class[T... 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.