A proposal to add some way to skip or include some delegates, using a syntax 
like:

<...  skip=${use-remote} ...>
<...   run=${use-remote} ...>

to pick among alternatives based on one setting (the "use-remote" value) could
be done with just one attribute:

<... run=${use-remote} ...>
<... run=${use-local}  ...>

The downside to this is that users would have to set 2 variables, one to true,
the other to false, every time they wanted to change this.

By introducing a bit of expression syntax and conditional assignment into the
syntax for the external configuration, we can get back the ability to have just
one edit change the setting. 

a possibilities:

    use-remote = true
    use-local = ! ${use-remote}

This is, surprisingly, possible with the current implementation of external
overrides, now:

    nottrue = false
    notfalse = true

    use-remote = true
    use-local = ${not${use-remote}}

But I would argue that this is less readable by normal people :-).

The downside of introducing expression syntax into the configuration file is
that it then starts to have the disadvantages of programming languages - that
is, you can make mistakes :-), and it takes a higher-level-of-skill (generally).

I think it could be a bit of a slippery slope to go down this path - the
expression language begins to get bigger, then you need more error reporting,
maybe a debugger, a "findbugs" checker, etc. :-)

-Marshall

Reply via email to