> 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 the file control body appear (although it should probably appear at the top to make things clear). > So, when can I expect the "other" scope selector to also support being a > colon, removing the confusion that I regularly see between using period for > two different things? ;) Actually that change happened already, I just realized the documentation has not been updated. The namespace separator is now a colon, in the most recent checkout from github. --Diego _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
