On 8 April 2013 12:31, Erik Dalén <erik.gustav.da...@gmail.com> wrote:
> > > On Friday 5 April 2013 at 20:26, henrik lindberg wrote: > ... > > I hope we can correct the fundamental ones in the Puppet 4.0 evaluator > > (there are smells around undef, possibility to alter immutable > collections, around certain comparisons, and a few more corner cases - i.e. > things that are difficult/impossible to support more than one way at the > same time). > > This sounds very good. Might be better having a global change to all these > behaviours than a configuration switch for each one of them. > Perhaps this could work in a similar way to the Perl 'use strict' pragma where you can turn on all the strict checks or just the ones you want (eg. 'use strict vars') and turn off the ones you don't want (eg. 'no strict refs'). > > This work makes it possible for different modules to use different > compliance levels! It is only the fundamentals that must be the same across > all versions. To me this is perhaps the most important goal. Going forward > it is unreasonable to expect that all forge modules must be updated at the > same time in order for a user to adopt a newer version of puppet. > > How would that work? Should you specify the parser and evaluator to use > (or language version) in your Modulefile? Seems hard to me technically to > share state between multiple versions of the evaluator. > I expect this would have to be as lenient as required to parse and evaluate all modules that are loaded, probably with a cache so this doesn't have to be determined every time. > -- > Erik Dalén - Keith -- 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 post to this group, send email to puppet-dev@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
