Issue #21874 has been updated by Henrik Lindberg.
I think I have an approach how to solve this. I made an experiment, which differentiates between: <pre> somename[1] somename [1] </pre> Where: * the first is interpreted as "deprecated resource reference" (i.e. reference to resournce titled '1' of type 'somename'). * the second is NAME followed by list of arguments (there is only one), the first arg is a literal list (in this case containing the number '1' Although I really do not like having significant whitespace, there is really no other way. My experiment works in practice and involves some lexer magic... - will clean that up and make a PR. ---------------------------------------- Bug #21874: Enabling --parser future causes classes to be not found and other errors https://projects.puppetlabs.com/issues/21874#change-99238 * Author: Lee Lowder * Status: Accepted * Priority: Normal * Assignee: Vasiliy Boulytchev * Category: compiler * Target version: * Affected Puppet version: 3.2.2 * Keywords: future_parser customer * Branch: ---------------------------------------- (from a customer) After setting parser = future in puppet.conf, code that was working now causes errors. Sample error: undefined method `value' for Puppet::Pops::Model::AccessExpression:Puppet::Pops::Model::AccessExpression at /etc/puppetlabs/puppet/modules/.../manifests/logic.pp:24 (code sample is in the support ticket, will be linked to in a comment) -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
