On Mon, Apr 23, 2012 at 3:22 AM, C.Koy wrote:
> On 4/22/2012 11:32 PM, Galen Wright-Watson wrote:
>
>> 2012/4/22 C.Koy
>>
>> On 4/21/2012 4:37 AM, Galen Wright-Watson wrote:
>>>
>>
>> But, I did not start this thread to discuss such bug fix, because:
>>>
>>> 1. It does not take a genius to figu
On Mon, 2012-04-23 at 18:39 +0200, jpauli wrote:
>
> 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.
Every(*) PECL extension does.
(*) The exception proves the rul
+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_VERS
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
Heya,
It appears that many extensions do not expose proper version information.
Here an abstract of the various things I found using the following script:
$ for i in `php -m`; do php --re $i | grep "$i version"; done
curl
date 5.4.0
dom 20031129
mysqlnd mysqlnd 5.
On 4/22/2012 11:32 PM, Galen Wright-Watson wrote:
2012/4/22 C.Koy
On 4/21/2012 4:37 AM, Galen Wright-Watson wrote:
But, I did not start this thread to discuss such bug fix, because:
1. It does not take a genius to figure it out, and should take minutes to
implement for someone experienced i
