+1 for that notice. In fact, Zend API provides extensions a char* to give a hint about the extension version, but I guess no-one has been serious and really used that field as it would have to be. I recently noticed mistakes in ext/mysqlnd_ms as well.
I then agree with Johannes, just use PHP_VERSION, and you can think about yourself as safe. Well, at least until a curious setup would compile PHP itself mixing extension versions in the same PHP Core version ... Cheers Julien.P 2012/4/23 Johannes Schlüter <johan...@schlueters.de> > On Mon, 2012-04-23 at 16:47 +0200, Jordi Boggiano wrote: > > As you see it goes from no version at all to proper versions, passing by > > svn revisions, dates, or a mix of all. > > > > In Composer [1] we try to parse all that using ReflectionExtension, to > > allow people to require some specific version of an extension if they > > want. Obviously this doesn't work very well when no version or some > > random revision number is provided. > > > > Is there any other way I overlooked to get more version info? If not, > > can this at least be improved in the future? > > For PECL extensions the version number should be fine (or you can hit > the package maintainer ;-) ). For core stuff i'd propose to switch to > PHP_VERSION as version everywhere. While this can be complicated for > extensions which are maintained in both (oci8 for instance) > > johannes > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
