On 22/08/06, Thomas Anders <[EMAIL PROTECTED]> wrote:
> Agreed in general. Still, where would you suggest to put the PACKAGE_*
> variables in that picture?
c) They're clearly generically named, but the values are Net-SNMP specific.
> Actually, they look too problematic to be put anywhere. :-(
Put them in the c) block, (whether this is a separate file, or part of
an a+c header),
and protect them with a suitable #if{n,}def statement.
Something like
#ifndef OMIT_PROBLEMATICAL_SETTINGS
#define PACKAGE_NAME "Net-SNMP"
#define PACKAGE_VERSION "5.4.3.2.1"
#define PACKAGE_STRING "Thunderbirds are Go"
#endif
Most people don't need to worry about this, and can just carry on
working as before.
Anyone who needs to combine two autoconf-based libraries into the same
application can
#define OMIT_PROBLEMATICAL_SETTINGS
before including the two config header files, and sort out the overlap manually.
But they'd *only* have to worry about the overlap - they should be
able to use everything else as usual. That feels better than saying
"you do it our way, or you're on your own".
Dave
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
