On Friday 21 January 2011, Nick Gearls wrote:
> Using extensively mod_define, mod_macro and rewrite maps in very
> big environments, I personally chose for ~{...} to be safe.
> But, as far as we can change it, everyone can choose what they
> want.
I haven't implemented that so far, but it would not be much work. What
configuration syntax is preferred? mod_define's
Define define::open (
...
or something that doesn't overload Define, like
ConfigVarExpansion BraceOpen=( ...
or
ConfigVarMetaChars "~()"
Opinions and suggestions for better names are welcome.
FTR, there are some differences in behaviour compared to mod_define.
Therefore adopting mod_define's syntax may only cause wrong
expectations:
- There is no escape char.
- A variable gets valid immediately after the Define statement, as
opposed to mod_define collecting all defines and then applying the
final state in a second pass through the config. Together with
Include, this behaviour may even be used as a poor man's mod_macro.
- Warning messages about undefined vars don't have file name/line
number info (that is not available at that point, unfortunately).
