Unfortunately, this has never been well defined, but I will give the intent.
APR_HAS_* --> APR supports this feature APR_USE_* --> APR uses this particular feature as the default APR_HAVE_* --> These are supposed to be just namespace protected versions of the autoconf macros. The problem is that all autoconf programs use the exact same macros, so if two projects use autoconf, there is collision. Ryan ---------------------------------------------- Ryan Bloom [EMAIL PROTECTED] 645 Howard St. [EMAIL PROTECTED] San Francisco, CA > -----Original Message----- > From: Miguel Camargo [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 12, 2002 9:26 AM > To: [email protected] > Subject: APR doubts > > Hello: > > I am trying to modify the APR library just to add some specific features > in > it and use it in Apache. But i have some doubts about the meaning and the > differences among the macro definitions of: > > APR_HAVE_... > APR_USE_... > APR_HAS_... > > In which cases i have to use one of this, which are their different > meanings? I ask that because i want to add a new feature (with a header > file) and i don�t know if i should add a macro definition like this: > APR_HAVE_NEWFEATUREH. And also i don�t konw if i have to check in the code > : > #if APR_HAS_NEWFERATURE ... to compile or not the feature. > > I am really lost about all of this and i'll be very pleased of any kind of > help. > > thank you! > > > > > > _________________________________________________________________ > Env�e y reciba su correo de Hotmail desde el m�vil: http://mobile.msn.com
