On 2014-03-16 01:36, Henrik Lindberg wrote:
Sure experienced programmers or people who are more familiar with how
the scoping model in Puppet works will be able to use this to their
advantage but the code that's produced and potentially released might
not be easy to understand for others.
Yeah, and how it works today is a mystery to most Puppet Users, even
experts are tripped up by some of the quirks.
Yes.
It will interesting to see how the different ideas works in practice. We
have a goal to "not break every module" in the initial release of 4x,
and having the new simpler/stricter lookup rules may be too much
breakage to tolerate and we have to introduce a "legacy name resolution"
option or something like that to help migration. Whatever we do we need
to make sure that a well formed 4x (not using any other new 4x features)
also work on 3x.
In the worst case, you could add a special "option strict"[1] sigil, to
request strict lookup on a file-by-file basis for as long as "legacy"
lookup has to be supported.
Would probably be a nightmare to support by the implementation though.
[1]http://stackoverflow.com/q/2454552
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/532559CC.6050007%40dasz.at.
For more options, visit https://groups.google.com/d/optout.
