Re: cvs: php4 /ext/standard Makefile.in basic_functions.c php_standard.h php_versioning.h versioning.c

I think a capabilities scheme is more elegant, but it requires a lot of careful planning and foresight that I honest don't think we have yet. A staged numbering scheme for the API only describes one capability: interoperability. This is less informative, but IMHO describing for both humans and programs what interoperability you can expect from a release is the single most important thing. It's also a lot more simple to understand and implement, which is a strong plus right now. I'll leave room for a capabilities system in the future in the PEAR framework. - Stig [Andi Gutmans <andi@zend.com>] > Are you sure you want to go with a format of x.y.z? Doesn't something > like I suggested (with more information) make things easier? > I think the main question is if x.y.z has all of the version > information you guys need. > > Andi > > At 11:56 PM 10/5/2001 +0000, Stig Bakken wrote: > >ssb Fri Oct 5 19:56:20 2001 EDT > > > > Added files: > > /php4/ext/standard php_versioning.h versioning.c > > > > Modified files: > > /php4/ext/standard Makefile.in basic_functions.c php_standard.h > > Log: > > * prototype of version_compare, doesn't work yet > > > > > >-- > >PHP CVS Mailing List (http://www.php.net/) > >To unsubscribe, e-mail: php-cvs-unsubscribe@lists.php.net > >For additional commands, e-mail: php-cvs-help@lists.php.net > >To contact the list administrators, e-mail: php-list-admin@lists.php.net -- Stig Sæther Bakken <ssb@alltheweb.com> Fast Search & Transfer ASA, Trondheim, Norway