On 19/06/07, Wes Hardaker <[EMAIL PROTECTED]> wrote: > Patch 1737727 brings up an interesting (as always) conflict dilemma. > Anyone have thoughts on it?
The obvious approach would be something like: #define NETSNMP_OLDAPI_RONLY 0x1 #define NETSNMP_OLDAPI_RWRITE 0x2 #define NETSNMP_OLDAPI_NOACCESS 0x3 #ifndef NETSNMP_CLEAN_NAMESPACE #define RONLY NETSNMP_OLDAPI_RONLY #define RWRITE NETSNMP_OLDAPI_RWRITE #define NOACCESS NETSNMP_OLDAPI_NOACCESS #endif Dave ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
