Jira (PUP-979) future parser fails to recognize hash as parameter in un-parenthesized calls

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: future parser fails to recognize hash as parameter in un-parenthesized calls The fix for the actual problem reported in this issue (allow hash to be argument to notice) is simple and can go into 3.5.0 - will merge this as it is not fun to deal with merge conflicts in the grammar and generated parser going forward. Add Comment   Puppet / PUP-979 future parser fails to recognize hash as parameter in un-parenthesized calls If an attempt is made to evaluate this {code} notice {a => 10} {code} The result is the error message: "ll resource specifications require names" This is because it was once allowed to have resource initialization without a name, and the parser issues a deprecation error for this. This is somewhat tricky to work around as the grammar does not ... 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.