We have many examples of configure checks that drive #ifdef'ed code to take care of minor differences between versions of a library. Are the changes really so significant that we can't do this cleanly here?
-Rasmus On Thu, 5 Sep 2002, Harrie Hazewinkel wrote: > HI, > > I was working on getting PHP with SNMP compiled with the > latest NET-SNMP 5.0.4 (was UCD-SNMP). It does not work. > I was willing to fix this problem, however, I beleive it > could cause backwards compatibility problems if the > UCD-SNMP must be kept. > > the options are (as i recognise), > 1) drop UCD-SNMP support since the NET-SNMP is just the name change > plus many other good features. > 2) Make sure both work with IFDEF's. > 3) Add an extra SNMP portion that works with NET-SNMP. > > > Personnally I think 1 would be the best choice, but I have also > created once an SNMPv3 extension for PHP with SNMP and therefore > 3 could be choosen and have then the new SNMPv3 features. > > > What do others think?? > > > Harrie > > Internet Management Consulting > mailto: [EMAIL PROTECTED] http://www.lisanza.net/ > -------------------------------------------------------------------- > Author of MOD-SNMP, enabling SNMP management the Apache HTTP server > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
