>>>>> On Fri, 17 Apr 2009 23:33:18 +0200, Magnus Fromreide >>>>> <[email protected]> said:
MF> I'd like to make the compilation of the MF> checkmib() The only problem I can see with that is that people may have existing code out there that uses checkmib(). We have untold numbers of third-parties with very old mib code out there that isn't actively maintained. It's always been my dream that they at least are willing to track the latest base package to get upgraded support and fixes even if they don't touch their own MIB code much. We have huge issues with people not willing to upgrade beyond some ancient release. That being said, I don't like leaving old code around either if we can help it but I do realize that we may encourage yet more people to using versions after 5.4 because of dropped support for functions once considered valid. So, my return question would be: what's the downside of leaving it? What's the downside of leaving it but defining it to be something very simple (like a function wrapper as you proposed). Or what's the downside of turning it into a macro so it has no compiled code unless used? In the end, I'm on the fence. -- Wes Hardaker Please mail all replies to [email protected] ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
