Just FYI, there is some discussion of a partially-overlapping concern going
on in this ticket:
http://projects.puppetlabs.com/issues/13210
On Wed, May 2, 2012 at 12:04 PM, Dan Bode wrote:
>
>
> On Wed, May 2, 2012 at 9:11 AM, Andrew Parker wrote:
>
>> It can also be asked as "is passing nil or
On Wed, May 2, 2012 at 9:11 AM, Andrew Parker wrote:
> It can also be asked as "is passing nil or undefined as the value of a
> class parameter the same as not specifying that class parameter at the
> point of use at all?"
>
I am pretty sure that this behavior as it relates to undef is already
s
It can also be asked as "is passing nil or undefined as the value of a class
parameter the same as not specifying that class parameter at the point of use
at all?"
This way of phrasing it makes me think twice about this behavior, because it
now means that you can't look just at the point of us
So, I dopped into the debugger with:
$x = inline_template("<%= require 'ruby-debug';debugger;puts 'foo' %>"
and realized that the value returned from the statement:
$var1_override = $override_hash['var1']
is actually nil.
So an easier version of my question is rather or not nil can be treate
