httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rodent of Unusual Size <Ken.C...@Golux.Com>
Subject Re: More function naming conflicts
Date Fri, 06 Feb 1998 16:15:31 GMT
Rasmus Lerdorf wrote:
> Somebody somewhere is really out to get me.  The latest Solid (an RDBMS)
> libs have no less than 5 function naming conflicts with Apache.  I don't
> see why in the world they have a "send_http_header" function for example,
> but something like "process request" is way too generic a name for Apache
> to have as a non-static function.  It would be nice if every single
> non-static Apache function was clearly labelled with whatever prefix it
> was we decided on for these things.

Hmmph.  I don't see why *they* can't label *their* functions..

Oh, well.  The question's open again.  We've got these, and palloc(),
and wasn't there another one as well?  Let's have another round of
discussion on temporary (1.3) prefixes, shall we?

#ken	P-)}

View raw message