On Thu, 2009-04-23 at 07:58 -0700, Wes Hardaker wrote: > >>>>> 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?
We could end up with more people using it (through cargo cult programming). Very little more code. > What's the downside of leaving it but defining it to be something very > simple (like a function wrapper as you proposed). It already is defined that way. > Or what's the downside of turning it into a macro so it has no > compiled code unless used? That the symbol disappears from the library so old code will have to be recompiled instead of just relinked. To reiterate - what I am suggesting is that if you build the library with CFLAGS=-DNETSNMP_NO_LEGACY_DEFINITIONS then checkmib shouldn't be defined. The gain is that the symbol disappears. This is also the risk. /MF ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
