Issue #21874 has been updated by Henrik Lindberg.

Without a reproducible example this is difficult to do anything about.

A hint is that the AccessExpression is the result of parsing `expression[ 
expressionlist ]` - so any expressions involving the `[]` operator is worth 
extra scrutiny.
Also, the problem may be a ruby runtime problem, it may be worth making sure 
one of the supported ruby runtimes is used. (Many weird problems can occur 
otherwise).

The problem with a "variable without $" is a "bare word", and these are 
interpreted as function calls. The error one expects then is "unknown 
function". If some other error message was shown for that, please report that 
as a separate issue.

----------------------------------------
Bug #21874: Enabling --parser future causes classes to be not found and other 
errors
https://projects.puppetlabs.com/issues/21874#change-98547

* Author: Lee Lowder
* Status: Needs More Information
* 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.

Reply via email to