Hi all,

I'm reviewing a ticket related to how we handle "undef" when it is passed
to a puppet function.  The current behavior is to convert it to an empty
string before passing it off to the function body, but I'm not sure that's
the right thing to do as it seems to eliminate the ability to handle some
valid use cases where there is a semantic distinction between "undef" and
the empty string.

This behavior has been discussed before--about a year ago--and it seems
like there were some folks in favor of the current empty-string approach.
 I'd welcome comments on the ticket!

http://projects.puppetlabs.com/issues/13210

Thanks
Chris

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-dev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-dev?hl=en.

Reply via email to