On 14. mai 2016 01:30, [email protected] wrote: > One further thought on this: > > Looking down the road a bit, we may want to consider handling the "if" > attribute of a classes promise the same way as the "expression" > attribute, or vice versa. > > I would imagine that newcomers to CFEngine will have no particular > reason to ever use the "expression" attribute at all, when the default > expression is "any" and they can express the more complex conditionals > they will need with an "if" attribute (or an "and" attribute, or "or" > attribute, etc.) without ever learning "expression."
Good point, I never even considered that these two are essentially doing exactly the same thing. It would be possible to deprecate "expression" entirely, and it wouldn't even require introducing anything new. > Currently, the verbose output based on "expression" is different from > that based on "if" (example shown is running 3.7.1): Under the hood, the execution paths are different, so this is not surprising. I wouldn't be surprised if there are other, subtle differences as well, but this requires more investigation. -- Kristian -- You received this message because you are subscribed to the Google Groups "dev-cfengine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dev-cfengine/573C0BC1.8080705%40cfengine.com. For more options, visit https://groups.google.com/d/optout.
