You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "Roy T. Fielding" <fi...@kiwi.ICS.UCI.EDU> on 1999/08/24 06:22:28 UTC

STANDARD20_MODULE_STUFF

I am going to try to ask questions as I dig through the diffs
and old repositories when I can't find the rationale for a change.

The first is:  why change STANDARD_MODULE_STUFF to STANDARD20_MODULE_STUFF?
I mean the symbol name, not the contents.  Was there some significant
incompatibility, or is this just a way to break the compile of modules
that haven't been tested with 2.0 yet?

....Roy

Re: STANDARD20_MODULE_STUFF

Posted by Dean Gaudet <dg...@arctic.org>.
btw, yeah there was a significant incompatibility -- i added a bunch of
new methods, not at the end of the structure... and then ben changed
everything to use hooks

but in general, i deliberately change symbol names when i intend to break
source compilations, and 1.x to 2.x is supposed to break source
compilations, so that change was made right away. 

Dean

On Mon, 23 Aug 1999, Dean Gaudet wrote:

> it was a way to break compiles.
> 
> On Mon, 23 Aug 1999, Roy T. Fielding wrote:
> 
> > I am going to try to ask questions as I dig through the diffs
> > and old repositories when I can't find the rationale for a change.
> > 
> > The first is:  why change STANDARD_MODULE_STUFF to STANDARD20_MODULE_STUFF?
> > I mean the symbol name, not the contents.  Was there some significant
> > incompatibility, or is this just a way to break the compile of modules
> > that haven't been tested with 2.0 yet?
> > 
> > ....Roy
> > 
> 
> 


Re: STANDARD20_MODULE_STUFF

Posted by Dean Gaudet <dg...@arctic.org>.
it was a way to break compiles.

On Mon, 23 Aug 1999, Roy T. Fielding wrote:

> I am going to try to ask questions as I dig through the diffs
> and old repositories when I can't find the rationale for a change.
> 
> The first is:  why change STANDARD_MODULE_STUFF to STANDARD20_MODULE_STUFF?
> I mean the symbol name, not the contents.  Was there some significant
> incompatibility, or is this just a way to break the compile of modules
> that haven't been tested with 2.0 yet?
> 
> ....Roy
>