On 2015-23-03 19:50, Wil Cooley wrote:
On Mon, Mar 23, 2015 at 11:37 AM Wil Cooley <wcoo...@nakedape.cc> wrote:
I see now too that I was not just being lazy; neither the
"Functions" section of the Language Guide nor the Custom Functions
Guide -- searching for "undef", "null", "empty" and "return" does
not yield this datum:
I spoke too soon: There's a table at the bottom of the "Functions"
section of the Language Guide that has both "empty" and "undef"; I dunno
how I missed it. (Somehow I also thought that I could return :undef from
Ruby to get an undef in Puppet; I'm not sure where that came from.)
That may or may not work... it sort of depends where that value gets used.
In future parser and with the 4x function API, there is no ambiguity,
the functions get Ruby nil for puppet undef, and should return Ruby nil
for puppet undef, and empty strings have no magic properties.
- henrik
--
Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/mf1boq%24nkq%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.
