On Wed, Apr 3, 2013 at 8:10 AM, Xinchen Hui wrote:
> 发自我的 iPhone
>
> 在 2013-4-3，13:56，Hannes Magnusson 写道：
>
> > Wait wait wait. You are introducing a constant that is going to be
> > available as of 5.4.15 to 5.4.2x and then removed (as it looks like we
> > are agreeing)?
> how could that be?
发自我的 iPhone
在 2013-4-3，13:56，Hannes Magnusson 写道：
> Wait wait wait. You are introducing a constant that is going to be
> available as of 5.4.15 to 5.4.2x and then removed (as it looks like we
> are agreeing)?
how could that be? This constant will in the final release of 5.5.0.
Thanks
>
> Peopl
Wait wait wait. You are introducing a constant that is going to be
available as of 5.4.15 to 5.4.2x and then removed (as it looks like we
are agreeing)?
People have been living without this constant forever now so people
have their workarounds in place and no need to complicate their code
to for t
On Tue, Apr 2, 2013 at 9:14 PM, Rasmus Lerdorf wrote:
> On 04/02/2013 07:52 PM, Sara Golemon wrote:
> > https://wiki.php.net/rfc/php-array-api
>
> Very nice. I would love to see more of the API simplified for common
> tasks like this. It is a macro jungle currently.
>
> -Rasmus
>
Coming from a mo
On 04/02/2013 07:52 PM, Sara Golemon wrote:
> https://wiki.php.net/rfc/php-array-api
Very nice. I would love to see more of the API simplified for common
tasks like this. It is a macro jungle currently.
-Rasmus
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
https://wiki.php.net/rfc/php-array-api
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Added new constant CURL_WRAPPERS_ENABLE in (include 5.4)
https://github.com/php/php-src/commit/d7f709a032a40cb475042b43db07a4698a2488b7
thanks
On Mon, Apr 1, 2013 at 9:53 PM, Laruence wrote:
>
>
>
> On Mon, Apr 1, 2013 at 7:18 AM, Hannes Magnusson <
> hannes.magnus...@gmail.com> wrote:
>
>> O
On 2013-03-31 00:27, Stas Malyshev wrote:
Hi!
I think Stas proposes a solution to the problem and I think Anthony
proposes a viable alternative. I would say that Anthony has found the
shortest distance between the two points (the problem and the solution),
however.
The fact is that people do
hi,
On Thu, Mar 14, 2013 at 4:32 PM, Anatol Belski wrote:
>> One doubt I have yet after investigating on #62852 is that issuing
>> php_error isn't recoverable, it might be much better to throw exception in
>> __wakeup(), just like __construct() does. This question crosses both
>> #62852 and #5
On 2 April 2013 11:36, Michael Wallner wrote:
> On 2 April 2013 08:50, Rasmus Lerdorf wrote:
>
>>
>> Looks like these ASN1_STRING_to_UTF8 ones are normal for libcrypto.
>> Really hard to debug openssl stuff with all these Valgrind false
>> positives. Still trying to track down the core on Centos
On 2 April 2013 11:36, Michael Wallner wrote:
> On 2 April 2013 08:50, Rasmus Lerdorf wrote:
>
>>
>> Looks like these ASN1_STRING_to_UTF8 ones are normal for libcrypto.
>> Really hard to debug openssl stuff with all these Valgrind false
>> positives. Still trying to track down the core on Centos
On 2 April 2013 08:50, Rasmus Lerdorf wrote:
>
> Looks like these ASN1_STRING_to_UTF8 ones are normal for libcrypto.
> Really hard to debug openssl stuff with all these Valgrind false
> positives. Still trying to track down the core on Centos 6.2. Looks like
> a weird build issue at this point.
>
12 matches
Mail list logo
