All syntax checks are done inside mod_macro.
I agree that changing the syntax would be cleaner, but that would
probably take some time.
Until that, a warning is better than nothing, no? We could also raise
the warning to an error but I suppose some peopel may complain about
backward compatibili
On Thu, Oct 6, 2016 at 3:04 AM, Nick Gearls wrote:
>> I don't think mod_macro should emit a warning for its own basic
>> configuration
>
> That's what it currently does (in 2.4)
Isn't it the core currently and not mod_macro? Which is why my
preference is to advocate a syntax that isn't ambiguou
I don't think mod_macro should emit a warning for its own basic configuration
That's what it currently does (in 2.4)
it happens to overlap with the cores variable expansion
That's indeed a bad choice - this is why I propose a warning
Forwarded Message
Subject:Re: Un
BOOL - fixed :-(
Forwarded Message
Subject:Re: mod_macro: Control on bad nesting
Date: Wed, 5 Oct 2016 09:54:43 -0400
From: Jim Jagielski
To: dev@httpd.apache.org, nickgea...@gmail.com
'bool' ??
On Oct 5, 2016, at 8:50 AM, Nick Gearls wrote:
The proposed
