Issue #22528 has been updated by Henrik Lindberg.
And... I just made it worse. The reject function (in stdlib) is shadowed by reject in core. To fix this, I made reject support being called like the reject in stdlib. (The documentation in the function clearly describes this). Seems like the lookup function will be removed - so back to "one future" I still think it is enough with a "since", and marking future / conditional in the tag, i.e. "since 3.3.0 - when using future parser" or somesuch..., or including the word "experimental", say "experimental since 3.3.0, applicable when using future parser" ---------------------------------------- Bug #22528: Functions that require the future parser should be concretely identifiable https://projects.puppetlabs.com/issues/22528#change-98545 * Author: Nick Fagerlund * Status: Accepted * Priority: Normal * Assignee: * Category: * Target version: * Affected Puppet version: * Keywords: * Branch: ---------------------------------------- Take a look at the function reference: http://docs.puppetlabs.com/references/3.latest/function.html There are a bunch of functions in there that will just plain explode on a stock Puppet 3.x install. (each, collect, etc.) This is because there's no indication in these functions' code that they require the future parser. We need an indication of this built into the function API, not only for the sake of documentation but also to improve error handling, etc. -- 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.
