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: Unexpected Warnings from Macro Use in 2.4
Date: Wed, 5 Oct 2016 09:57:31 -0400
From: Eric Covener <[email protected]>
To: Apache HTTP Server Development List <[email protected]>,
[email protected]
On Wed, Oct 5, 2016 at 8:48 AM, Nick Gearls <[email protected]> wrote:
Nobody is interested in avoiding problems with this sanity check?
Trivial to review, only a warning - but that could save hours to users
I didn't see it the first time, but I don't think mod_macro should
emit a warning for its own basic configuration because it happens to
overlap with the cores variable expansion. I don't like it for 2.4.