Re: [Puppet-dev] RFC on #5158: Make source/content parameters and the file/template functions consistent.

2011-03-29 Thread Nigel Kersten
>> We just don't expose the syntax directly; instead of >> >> cat(template("a.erb"), template("b.erb") >> >> >> you write: >> >> "${template("a.erb")}${template("b.erb")}" >> >> >> and this is internally processed as a concatenation...so what you're >> suggesting is just a syntax-desugaring. I c

Re: [Puppet-dev] RFC on #5158: Make source/content parameters and the file/template functions consistent.

2011-03-28 Thread Nigel Kersten
On Mon, Mar 28, 2011 at 5:21 PM, Markus Roberts wrote: > > We’re also going to introduce a concatenation function called “cat”. >> > > Note there is already a concatenation operator in puppet (from > lib/puppet/parser/ast/leaf.rb): > > > class Concat < AST::Leaf > def evaluate(scope) >

Re: [Puppet-dev] RFC on #5158: Make source/content parameters and the file/template functions consistent.

2011-03-28 Thread Markus Roberts
> We’re also going to introduce a concatenation function called “cat”. > Note there is already a concatenation operator in puppet (from lib/puppet/parser/ast/leaf.rb): class Concat < AST::Leaf def evaluate(scope) @value.collect { |x| x.evaluate(scope) }.collect{ |x| x == :undef ? ''

[Puppet-dev] RFC on #5158: Make source/content parameters and the file/template functions consistent.

2011-03-28 Thread Nigel Kersten
We've gone back and forth on this for a while, I'd like us to get an implementation agreed upon. If the topic doesn't instantly make sense to you, please visit the bug for an overview of our current inconsistent behavior: http://projects.puppetlabs.com/issues/5158 Whenever an array is specified