httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexei Kosut <ako...@leland.Stanford.EDU>
Subject Re: [PATCH] new_connection -> ap_new_connection name change
Date Sun, 18 Jan 1998 22:21:51 GMT
On Sun, 18 Jan 1998, Ian Kluft wrote:

> Symbols beginning with underscores are reserved by some compilers for their
> own internal or machine-specific symbols.  While the chance of colliding
> with a compiler symbol of that name is probably small, the concept of
> cooperating with existing namespaces is probably well understood around here.

Agreed here.

> Is the group willing to consider explicitly redefining the meaning of ap_ to
> include any functions available via the Apache API?  There's probably no
> little of confusion with re-implemented Unix functions because, for example,
> ap_snprintf() would still mean "snprintf available through the Apache API".
> That sounds like a technically feasible and reasonably simple option.

Yes, but I personally have never liked particular combination of
characters "ap_". I think it looks ugly. So do we really have to have it
on *all* functions?

BTW, I just rememebered another way that the Apache code isn't
ANSI-compliant: ANSI/ISO C only requires external symbol names be unique
in a compiler/linker to six characters. Apache has functions that require
uniqueness to a much greater extent. All those getword* and
escape* functions, for example. Just a thought.

But then, we've had about as many problems due to that as we have with
NULL not being equal to zero (which we assume all over the place), so I
guess we can continue to ignore it.

-- Alexei Kosut <akosut@stanford.edu> <http://www.stanford.edu/~akosut/>
   Stanford University, Class of 2001 * Apache <http://www.apache.org> *



Mime
View raw message