On Mon, 2010-02-08 at 15:05 -0800, Luke Kanies wrote: > Ugly, but +1. The only alternative I can think about is to create some ephemeral scopes that deals only with ephemeral variables and delegates the rest to the regular scope. Then we can spawn a new ephemeral scope as soon as we encounter an evaluate_match (and get rid of it when returning). The only issue is that would require all AST.evaluate(scope) methods to also return a scope (possibly an ephemeral one), which is what I didn't want to do.
Hmm, another alternative would be to hook an ephemeral scope hierarchy to the current scope; evaluate_match would then spawn a new ephemeral scope which would "alias" the previous one in the same scope. That would be the cleanest solution. I'll see if I can come with a patch tonight. Thanks > On Feb 8, 2010, at 11:19 AM, Brice Figureau wrote: [snip] -- Brice Figureau Follow the latest Puppet Community evolutions on www.planetpuppet.org! -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
