Re: patch 1737727 and the NOACCESS #define

Hey,

Would like to raise this question to the top of the stack once more.
It has evolved into two questions.

- Do we want to move the RONLY, RWRITE, NOACCESS defines?
- Which of NETSNMP_NO_LEGACY_DEFINITIONS or NETSNMP_CLEAN_NAMESPACE do
we use to hide the old defines.

For the first question I could submit a patch with the following contents:

DS> #define NETSNMP_OLDAPI_RONLY 0x1
DS> #define NETSNMP_OLDAPI_RWRITE 0x2
DS> #define NETSNMP_OLDAPI_NOACCESS 0x3
DS>
DS> #ifndef NETSNMP_NO_LEGACY_DEFINITIONS
DS> #define RONLY NETSNMP_OLDAPI_RONLY
DS> #define RWRITE NETSNMP_OLDAPI_RWRITE
DS> #define NOACCESS NETSNMP_OLDAPI_NOACCESS
DS> #endif

About the second quesion: 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.

Do we also want a patch which converts all NETSNMP_CLEAN_NAMESPACE
into NETSNMP_NO_LEGACY_DEFINITIONS? I don't have access to subversion
here. Who introduced NETSNMP_CLEAN_NAMESPACE in revision 15493? Where
can he/she be reached?

Cheers,
Thijs

-------------------------------------------------------------------------
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
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders