yes, but this branch is trunk and is not supposed to be 5.2 compatible. If you want to get it out with previous versions support, then go through pecl as well. But without such external releases it will just clutter the codes.
Cheers, On Tue, Feb 1, 2011 at 9:51 AM, Lytochkin Boris <lytbo...@gmail.com> wrote: > Hi. > > I use this module in my production Cacti environment, which uses 5.2 branch. > As I use FreeBSD, I'm able to build snmp extension separately from > base php as .so module and I use this possibility :) > > As long as Cacti would need 5.2 to run I will mantain those ugly > checks (I believe this legacy will be corrected in next Cacti > release). > That is the only reason to make ext/snmp module be backwards > compatible down-to php5.2 > > On Tue, Feb 1, 2011 at 11:34 AM, Pierre Joye <pierre....@gmail.com> wrote: >> hi, >> >> I wonder why you need that as we don't release snmp outside php. I >> would suggest to either drop these backward compatible checks (cleaner >> code) or consider to do release through pecl as well and then these >> checks make sense. >> >> Cheers, >> >> On Tue, Feb 1, 2011 at 9:20 AM, Boris Lytochkin <lytbo...@php.net> wrote: >>> lytboris Tue, 01 Feb 2011 08:20:13 +0000 >>> >>> Revision: http://svn.php.net/viewvc?view=revision&revision=307898 >>> >>> Log: >>> preprocessed changes made in rev.307894: >>> keeping ext/snmp backwards compatible >>> >>> Changed paths: >>> U php/php-src/trunk/ext/snmp/snmp.c >>> > > -- > Boris > -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
