+10, shipit for both.
setting trusted_node_data turns "$facts" into a reserved variable and
triggers a nice warning as such if you try to use it. Seems that such
behavior should happen automatically for any reserved word (in puppet4, I
assume).
On Sat, Jul 19, 2014 at 4:44 AM, David Schmitt wro
On 2014-07-18 03:00, Henrik Lindberg wrote:
Hi,
Boolean Attributes
---
Exported with whitespace
---
Kill both with fire.
Please.
Regards, David
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To unsubscribe from this group and sto
- Original Message -
> From: "Peter Meier"
> To: puppet-dev@googlegroups.com
> Sent: Friday, July 18, 2014 8:47:59 AM
> Subject: Re: [Puppet-dev] RFC - Grammar quirks I want to remove...
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> >
On Fri, Jul 18, 2014 at 12:47 AM, Peter Meier
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 "progr
On 07/18/2014 09:47 AM, Peter Meier wrote:
>> 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.
I second this.
>> >
-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.
> Can we disallow white
Hi,
Boolean Attributes
---
The current grammar (and future parser) accepts an attribute operation
with the name being a Boolean value. Have you ever seen $true or $false
as parameters in a class, define or type?
i.e.
define foo ($true) {
}
foo { the_foo: true => false }
Can we get rid o
