On Fri, Mar 6, 2015 at 1:20 PM, Graham Leggett <[email protected]> wrote:
>
> If we did that I believe we’d just have an explosion of directives and
> confusion.
Yes of course, I see the interest of reusing as is.
But maybe introduce a new type of quote, with a prefix (let's say %),
like %"an %{expression} string" vs. "a plain text where %{expression}
is not expanded".
We would now have an issue with existing tokens (not quoted) starting
with %" (and some inconsistency with existing directives that accept
expressions without it)...
But that maybe could be(come) a general rule in the configuration some
day (handled generically at config time?), which any directive would
take advantage of (those which don't use/need/have a request_rec to
exec() the expression could use the original pattern/plaintext).
That's probably quite some work, but in the meantime any individual
directive could handle this itself (and disambiguate from now).
Maybe I'm diverging (and overlooking/engineering this), but it sounds
pleasant to have native expression support from the configuration, and
ease of use in modules (without the need to do it yourself).
