Dave Shield schrieb:
> I'm inclined to suggest that the problematic #defines are protected by
> #ifndef NETSNMP_NO_LEGACY_DEFINITIONS
> 
> and that the config also sets up
> 
> #ifdef NETSNMP_CLEAN_NAMESPACE
> #define NETSNMP_NO_LEGACY_DEFINITIONS
> #endif

Agreed.

>> I don't have access to subversion here. Who introduced
>> NETSNMP_CLEAN_NAMESPACE in revision 15493?
> 
> That would be Thomas.
> As was NETSNMP_CLEAN_NAMESPACE in r15194.
> (Which is why I phrased the question in the way I did!)

As for NETSNMP_CLEAN_NAMESPACE, I think I've checked in a patch proposed 
by someone else, but I'm taking full responsibility anyway (especially 
for forgetting that I've introduced NETSNMP_NO_LEGACY_DEFINITIONS 
earlier). The above should provide a clean fix, though.


+Thomas

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to