Are there already existing reserved local variable names? I don't know of any and I'd be resistant to starting this trend just for versioning.
Should this simply be a best practice? In other words, what exactly does reserving the word gain us since, as Mark said, no matter how hard you try someone somewhere will be using that word (and maybe it's just me but I'd prefer to put metadata in an array anyway). -- Brian On Mar 15, 2012, at 7:26 AM, Aleksey Tsalolikhin <atsaloli.t...@gmail.com> wrote: > On Thu, Mar 15, 2012 at 1:52 AM, Mark Burgess wrote: >> >> I have been thinking about the issue of metadata for bundles, e.g. such as >> author and version, and have been through a number of alternatives in my >> head, >> The problem I have with each of them is that they either change syntax in an >> ad hoc way to something that is not a natural promise, or they separate the >> metadata into a separate body. Neither of these seems acceptable. >> >> My best answer, which requires no immediate feature implementation is to do >> this by best practices, using reserved variables. >> >> vars: >> >> "bundle_author" string => "kermit"; >> "bundle_version" string => "1.2.3 frog legs"; >> >> These are private and can then be used as variables, and examined using >> functions $(bundle.bundle_version) for validation. > > Thank you, Mark. Metadata is variable so this solution fits the > existing framework very well. > > Sincerely, > Aleksey > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
