Forum: CFEngine Help
Subject: Re: CFEngine Help: Re: Namespace change
Author: sauer
Link to topic: https://cfengine.com/forum/read.php?3,27302,27384#msg-27384
Diego Zamboni Wrote:
---
> > So, when can I expect the "other" scope
>> Ok, thanks. Having a file control body works the same way as classes and
>> whatnot, where everything below that definition in the same file has a
>> namespace changed from default to whatever's specified? That's reasonable.
>
> Actually I think it applied to the entire file, regardless of
> Ok, thanks. Having a file control body works the same way as classes and
> whatnot, where everything below that definition in the same file has a
> namespace changed from default to whatever's specified? That's reasonable.
Actually I think it applied to the entire file, regardless of where t
Forum: CFEngine Help
Subject: Re: Namespace change
Author: sauer
Link to topic: https://cfengine.com/forum/read.php?3,27302,27379#msg-27379
Ok, thanks. Having a file control body works the same way as classes and
whatnot, where everything below that definition in the same file has a
namespace
Forum: CFEngine Help
Subject: Re: Namespace change
Author: zzamboni
Link to topic: https://cfengine.com/forum/read.php?3,27302,27349#msg-27349
sauer: name spaces are already in the documentation:
https://cfengine.com/manuals/cf3-Reference#Name-spaces
Forum: CFEngine Help
Subject: Re: Namespace change
Author: neilhwatson
Link to topic: https://cfengine.com/forum/read.php?3,27302,27348#msg-27348
Small discussion here.
https://cfengine.com/forum/read.php?3,26394,26416#msg-26416
___
Help-cfengine
Forum: CFEngine Help
Subject: Re: Namespace change
Author: sauer
Link to topic: https://cfengine.com/forum/read.php?3,27302,27346#msg-27346
Is there a link somewhere with a little more context around this? I've not seen
a lot of the design center discussions, but more controlled namespaci
As discussed with Ted Z. around the design center testing/use of
namespaces, we realize we could improve the consistency of the language
by reversing the decision to avoid ":" as the dereference operator and
change "." to ":", so we have
namespace:bundle_scope.variable_lval
as the hierarchy.
