On 24 January 2014 01:31, Henrik Lindberg <[email protected]>wrote:
> Thanks John for lots of good feedback, and I realize I should clarify some > things... comments inline below... > > > On 2014-24-01 24:46, John Bollinger wrote: > >> On Wednesday, January 22, 2014 12:15:31 PM UTC-6, henrik lindberg wrote: > > * How do we keep stdlib in sync with the Puppet version? >> >> >> >> Is it necessary to do so? Few of its functions seem dependent on Puppet >> internals, and none of those are among the ones that I think clearly >> belong as part of the core product. Most of those dependent on Puppet >> internals are in the group "dangerous_hacks" group. Yank those out, I >> say, and make them somebody else's problem. >> >> > Well, there is one big problem that we would like to solve, and that is > how functions are called. The ambition is to deal with this in Puppet 4 > timeframe. The problem with the current calling convention is (among other > things) that undef gets translated to an empty string - we would like to > stop transforming values that way. The idea is that a function can opt in > to the 4x calling convention. > > There may not be any functions in stdlib that will benefit from the > calling convention change though (have not reviewed for that yet). > > count, min & max would definitely benefit from that. They all make some ugly workarounds for it now. In the case of min & max it is mostly the conversion of numbers to strings (which only happens sometimes in puppet 3.x) they have to workaround. Will this also change in the 4.x function API, so numbers are numbers? -- Erik Dalén -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CAAAzDLdo_%3DhbK3XQxbAdQ74Hdqm7jrJTWaM521FCgDHFGDjbjg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
