httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Richards <p.richa...@elsevier.co.uk>
Subject Re: API version #define
Date Thu, 25 Apr 1996 16:31:09 GMT
In reply to Rob Hartill who said
> 
> > 
> > > #define APACHE_NEWAPI 1
> > 
> > 	Uh, let's make this real and do something like
> > 
> > #define APACHE_API	1.1
> 
> Shouldn't the API have its own version number if it undergoes
> significant changes?
> 
> It's not obvious looking at a module that requires 1.1 if that'll
> work for 1.1.9 or 1.6

yeah, the API should have a version number, it's the same principle
as shared libraries.

-- 
  Paul Richards. Originative Solutions Ltd.  (Netcraft Ltd. contractor)
  Elsevier Science TIS online journal project.
  Email: p.richards@elsevier.co.uk
  Phone: 0370 462071 (Mobile), +44 (0)1865 843155

Mime
View raw message