On 2014-18-07 17:42, Andy Parker wrote:
On Fri, Jul 18, 2014 at 12:47 AM, Peter Meier <peter.me...@immerda.ch
<mailto:peter.me...@immerda.ch>> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Can we get rid of this, it is bad enough that all other keywords
> can be used (if, unless, case, class, define, etc. etc.)
Couldn't we ban them as well? I think in most other "programming"
languages this won't work as well.
We tried that, accidentally, when we added some new keywords. Lots of
things broke. In fact one of the core types uses a keyword: exec uses
unless.
Yeah, there are a few that makes sense; "class", "unless", "define",
"type", "inherits", "not" comes to mind as possibly meaningful names
(there may be others). Since that is like half of them, we could just
support all of them. The keywords true/false are different in that they
produce boolean values. There is no great harm in continuing to support
them; I just find it odd to name an attribute "true" or "false", and we
already have confusion over "false" vs. false.
- 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
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/lqbg28%24oei%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.
