On Fri, 2007-03-02 at 10:14 +0100, Thomas Anders wrote: > We're fully open for suggestions on how to better handle this in the future.
I think it's typical to prefix #defines/functions in a manner so that the average user code will not conflict with any of the #defines/functions. So prefixing NETSNMP to each of the #defines will "flag" that they are netsnmp specific, thus the average user code can't conflict w/ it. I believe it's also common to prefix w/ "__" to indicate something is internal to a library. I'm not sure how painful this would be w/n the net-snmp code base, but I believe this is the "correct" way to deal with it. Al -- Albert Chu [EMAIL PROTECTED] 925-422-5311 Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
