Re: PR#677 - Apache won't compile w/C++

[Rodent of Unusual Size <co...@decus.org>]

    PR#677 complains that occurrences of "pool" elements in structure
    declarations keep him from being able to compile Apache with C++
    because they're declared as "pool *p" rather than "struct pool *p".
    Do we `warranty' Apache to be compilable with C++?  Or just ANSI C?
    Is it appropriate to make this change (doubtful), investigate it
    further (?), or just tell him we don't intend Apache to be
    C++-compilable?

    I'm not sure why this only applies to the pool elements - unless
    it's because all the other structures are declared in .h files but
    the actual pool structure is private to alloc.c..

    #ken    :-/}

Re: PR#677 - Apache won't compile w/C++

[Marc Slemko <ma...@worldgate.com>]

We have gone through this before a bit... the problem is that there is a
variable and a typedef or something with the same name.  Under C, the
namespaces are different.  They aren't under C++.

On Wed, 18 Jun 1997, Rodent of Unusual Size wrote:

>     PR#677 complains that occurrences of "pool" elements in structure
>     declarations keep him from being able to compile Apache with C++
>     because they're declared as "pool *p" rather than "struct pool *p".
>     Do we `warranty' Apache to be compilable with C++?  Or just ANSI C?
>     Is it appropriate to make this change (doubtful), investigate it
>     further (?), or just tell him we don't intend Apache to be
>     C++-compilable?
> 
>     I'm not sure why this only applies to the pool elements - unless
>     it's because all the other structures are declared in .h files but
>     the actual pool structure is private to alloc.c..
> 
>     #ken    :-/}
>