Oops...missed that part. Sounds good. I like it. -Tod
On Sep 3, 2010, at 4:32 PM, Daniel V. Klein wrote: > My complete proposal said "don't change the default behavior - only introduce > the new behavior if you add the special control variable". So, I think the > new behavior could safely be introduced without worry, as it would be turned > off by default. > > -Dan > > On Sep 3, 2010, at 7:19 PM, Tod Oace wrote: > >> On Sep 1, 2010, at 11:53 AM, Daniel V. Klein wrote: >> >>>> /^($(regexes))$/ # The slist contains strings, but they are >>>> expanded and then the result is interpreted as a regex >> >> I like that. It's very familiar syntax, and solves the problem you describe >> of controlling when regular expression matches happen. >> >> Special care would be needed when changing the behavior of existing string >> syntax though. Maybe a script to go scan and report possible regex strings, >> and make running that script a prerequisite to upgrading to the /regex/ >> version of cf-agent. Either that or introduce some new different syntax for >> non-regex strings along with // and keep the old "string" behavior the way >> it is for a while. >> >>> -Dan >>> _______________________________________________ >>> Help-cfengine mailing list >>> Help-cfengine@cfengine.org >>> https://cfengine.org/mailman/listinfo/help-cfengine >> >> -- >> Tod Oace, Intel Corporation <t...@intel.com> >> > -- Tod Oace, Intel Corporation <t...@intel.com> _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
