Re: general/5079: make install should not put include files into the "global namespace".

[wr...@apache.org]

[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]


Synopsis: make install should not put include files into the "global namespace".

Comment-Added-By: wrowe
Comment-Added-When: Thu Jun 22 18:21:06 PDT 2000
Comment-Added:

I am forwarding your message to the list for consideration.
Note that we are in the process of adding a significant 
amount of namespace protection to the future Apache 2.0
release, and have made strides in eliminating the non-ap_
identifiers, including for header files.

I have observed reports of clashes over the alloc.h name,
which is renamed ap_alloc.h in the forthcoming release of
Apache 1.3.13 - but do you have any examples of actual
conflicts with the other header names you cite?

Thank you for your report and interest in the Apache
server project!

Re: general/5079: make install should not put include files into the "global namespace".

[Peter Simons <si...@research.cys.de>]

>>>>> wrowe  writes:

 > I have observed reports of clashes over the alloc.h name, which is
 > renamed ap_alloc.h in the forthcoming release of Apache 1.3.13 -
 > but do you have any examples of actual conflicts with the other
 > header names you cite?

I don't recall any other problems; unfortunately it has been a while
since I tried to construct a $C_INCLUDE_PATH that will automatically
contain all installed 3rd party header files -- a project that failed
miserably. :-)

Just a proposal: IMHO the best way to avoid conflicts is to put all
include files into a directory for the project and then to address
them as <apache/alloc.h> etc., like X11, libgetline and a few others
do it. This has the further advantage that I can pull the includes
into the global include space just by adding a sym-link from
/usr/include/apache to whereever they actually live, thus avoiding the
need for setting CPPFLAGS explicitly at compile time. The ap_-prefix
admittedly does the job, too, but the separate directory strikes me as
the more elegant solution.

	-peter