I wasn't talking about the JSON support (but I can see why you thought I
did), I just think the following is a good idea:
Instead of writing this:
...
depth_search => recurse,
...
body depth_search recurse {
depth => "inf";
}
I would like something like this:
depth_search => { depth => "inf" }
This may increase the size and complexity of the cf3 parser, but it would
make my cf3 code clearer and less verbose. I cannot quite follow why this
isn't good knowledge management, but then again, I'm only using cf3
community as a tool to satisfy my needs for assuring consistent
configuration across servers, I'm not sure that qualifies as knowledge
management.
- Erlend
On 16 December 2011 08:06, Mark Burgess <[email protected]> wrote:
> ** Please forget you ever saw this.
>
> This might look superficially attractive to a programmer but it suffers
> from many problems, not the least of which would be a major increase in the
> size and complexity of the parser. This approach does not satisfy the
> criteria for good knowledge management. It appeals only to programmers -
> and would allow programmers to gratify themselves at the expense of
> communicating policy to other stakeholders.
>
> If there were ever a valid use case for sharing data as json, an
> intermediate function interface would be a defensible approach. Embedding a
> sub-language within cf3 would repeat the mistakes made in the cf2 which led
> to chaos and feature creep.
>
> The goal of cf3 core is to be small and stable. We are looking at other
> mechanisms to simplify body templating.
>
> --
> Sent from my Android phone with probably ridiculous and involuntary
> spelling corrections
>
> Erlend Leganger <[email protected]> wrote:
>>
>> 2011/12/14 Ted Zlatanov <[email protected]>
>>
>>>
>>> "$(crond)/cfrun"
>>> perms => "{ mode: 644, owners: ['root'] }";
>>>
>>
>> A definitive +1 - as a Perl user, I've always missed this syntax
>> shortcut. It's compact and readable - I can't see any drawbacks with it.
>>
>> - Erlend
>>
>
_______________________________________________
Help-cfengine mailing list
[email protected]
https://cfengine.org/mailman/listinfo/help-cfengine
