Ok, looks like it would be logical to change all three of them when any renaming is done. But having such generic defines in a header seems dangerous. At one point or another, there's going to be trouble...
On 6/19/07, Wes Hardaker <[EMAIL PROTECTED]> wrote: > > Patch 1737727 brings up an interesting (as always) conflict dilemma. > Anyone have thoughts on it? > > (note that NOACCESS is one of 3 defines that are potentially usable by > old-api implementations. RONLY and RWRITE being the other two, which > are definitely used) > > -- > Wes Hardaker > Sparta, Inc. > > ------------------------------------------------------------------------- > 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 > ------------------------------------------------------------------------- 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
