On 12/09/2007, Thijs Brouwer <[EMAIL PROTECTED]> wrote: > There was a short discussion about the > NETSNMP_CLEAN_NAMESPACE vs. NETSNMP_NO_LEGACY_DEFINITIONS. > It seems NETSNMP_NO_LEGACY_DEFINITIONS was there first, so I suggest > we take that one.
NETSNMP_NO_LEGACY_DEFINITIONS actually feels to be a subset of NETSNMP_CLEAN_NAMESPACE - in that a clean namespace covers API calls as well as #defines. 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 > Do we also want a patch which converts all NETSNMP_CLEAN_NAMESPACE > into NETSNMP_NO_LEGACY_DEFINITIONS? A patch to convert #defines would be sensible, yes. > 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!) Dave ------------------------------------------------------------------------- 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
