I should point out, that from looking through my copy of the mail
archives, this is now the third or fourth time that -X has been brought
up. The reason I am against this, is that I brought it up every other
time, and we always decided against doing the work, or at least the work
was never done, for one reason or another. I am sick of re-visiting the
same issues over and over and over again. We have had this discussion far
too often to be changing our minds yet again.
> > The !! was there by the way, because it solved a lot of bugs on many
> > platforms.
>
> I'd wondered about that myself. I guess doing !! ensures that the value
> is 0 or 1 and not 0 or non-zero? Whatever.
Basically, yes. We are ensuring that we have a boolean option.
>
> > In all, I am -0.9 for this patch, I won't veto it, but I don't want to see
> > it in the code. If we do put the -X back in, then remove -DONE_PROCESS.
> > Having both is just bogus.
>
> That may be, but IMHO it completely violates the principle of least
> astonishment to have -X vaporize. I wanted to use it one day a month or
> so ago, got an error message that it was an unknown flag [with no hint
> that it'd changed to -DONE_PROCESS] and had to actually go dig into the
> MPM source to figure out how to tell Apache what to go do with itself.
> To me, THAT'S bogus. At the very least, -X should give a hint that it's
> now -DONE_PROCESS or it should be really well documented somewhere
> (AFAICT, it's not currently documented... may be wrong about that).
It's documented in manual/upgrading.html
Ryan
_______________________________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
