On Mon, Jun 13, 2005 at 03:54:14PM +0100, Dave Shield wrote: > On Tue, 2005-05-31 at 18:31, Matthew Boehm wrote: > > > Renaming asterisk's function is out of the question, as is renaming > > snmpd's. How does one overcome this? > > I've just committed a patch to the main development tree, > that renames the offending routine in the Net-SNMP source, > while leaving an (optional) compatability wrapper. > So anyone with existing code should be unaffected, while > this particular clash could be avoided by using the new > "netsnmp_unload_module" call, and defining a suitable > NETSNMP_CLEAN_NAMESPACE preprocessor directive.
Would similar patches to remove other just as ugly warts be considered? My first choice to kill would then be the PACKAGE_* macros. What is the transition plan for deprecation of the old calls? This is actually a general question - how old code should be supported? /MF ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
