Re: [PATCH] Hide symbols to avoid namespace conflicts (take 2)

[Ben Hyde <bh...@gensym.com>]

Thank you!  Thank you!

I'm confused how this all works out in practice.

What I don't understand is how do we know this works
out in practice.  For example from my nm -g output on
sunos.
   00064a24 T _isalnum
   00002020 T start

isalnum is in there with all it's friends of course this
makes it choke when it gets to "#define isalpha(c) ..."
in ctype.  I guess I ought to track down where it came
from.

What is the pattern for when this is to be used?
  ? developers should run it when ever they add
    a new external symbol.
  ? it will be run as part of the release ritual.
  ? it will be run from time to time, not running it
    is no big deal.
  ? <> modules MUST be linked into httpd when this
    is run.

It might be easy to enhance it so it can be used
when HIDE=yes.

Should HIDE=yes be the default?  I'd lean toward yes
since I prefer things to "on" so they get tested
going forward.

This adds perl to the tools required of the Apache 
developer.

Again - thank you.

 - ben hyde

Re: [PATCH] Hide symbols to avoid namespace conflicts (take 2)

[Rodent of Unusual Size <Ke...@Golux.Com>]

Whoops!  Something just occurred to me - this could have nasty
repercussions if mod_so is used to pull in modules which were
linked with a different setting of -DHIDE from the core..

#ken	P-)}

Ken Coar                    <http://Web.Golux.Com/coar/>
Apache Group member         <http://www.apache.org/>
"Apache Server for Dummies" <http://WWW.Dummies.Com/