On 25.07.2010, at 18:05, Karoly Negyesi wrote:
>> So this sounds like "bc does not interest me as long it affects
>> me personally"
>
> You have this backwards. BC surely interests me but there is no BC,
> there is only a pretense of BC so why not break it as we see fit? And
> because of this p
> So this sounds like "bc does not interest me as long it affects
> me personally"
You have this backwards. BC surely interests me but there is no BC,
there is only a pretense of BC so why not break it as we see fit? And
because of this pretense I have asked not to stop supporting PHP 5.2.
Regar
I said 'stable'. Last I have seen http://pecl.php.net/package/apc the
latest stable was 3.0.19.
Regards
Karoly Negyesi
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Le 25/07/2010 17:15, Kalle Sommer Nielsen a écrit :
Hello
2010/7/25 Karoly Negyesi:'
Extensions. APC to this day does not have a stable release for PHP
5.3. Neither has XCache. I am not even sure how do you imagine
*anyone* much less everyone upgrading to 5.3 with a production site
without
Hello
2010/7/25 Karoly Negyesi :'
> Extensions. APC to this day does not have a stable release for PHP
> 5.3. Neither has XCache. I am not even sure how do you imagine
> *anyone* much less everyone upgrading to 5.3 with a production site
> without a stable code cache...?
You should check your so
hi Reindl,
On Sun, Jul 25, 2010 at 2:06 PM, Reindl Harald wrote:
> I really do not understand you
Please do not top post and (re) consider the tone of your posts, in
general. It could be a language barrier but we are here to discuss
technical issues in the most friendly way.
Cheers,
--
Pierre
I really do not understand you
First you would like to see a incomatible change
without any sense because you do not like some code
On the other hand you are crying about the changes in 5.3
because your code which can not live with it since
you ignored warnings long time ago
So this sounds like
Am 25.07.2010 11:17, schrieb Karoly Negyesi:
> This is a very interesting decision as 5.3.0, compatibility wise, is a
> major release. I always felt it was PHP 6.0 but it was not called so
> because there was a development branched called that (which was later
> abandoned).
This is simply not tr
Am 25.07.2010 11:44, schrieb Karoly Negyesi:
>>> Where previously the function would accept the by-value argument, a
>>> fatal error is now emitted.
>
>> Not sure about this one. Do you have an example please?
>
> Erm, you do realized that I copied that from the handbook page? Example:
>
> func
hi,
On Sun, Jul 25, 2010 at 11:44 AM, Karoly Negyesi wrote:
>>> Where previously the function would accept the by-value argument, a
>>> fatal error is now emitted.
>
>> Not sure about this one. Do you have an example please?
>
> Erm, you do realized that I copied that from the handbook page? Exam
> Extensions. APC to this day does not have a stable release for PHP
> 5.3. Neither has XCache. I am not even sure how do you imagine
> *anyone* much less everyone upgrading to 5.3 with a production site
> without a stable code cache...?
Sorry, apparently XCache 1.3 version does work with 5.3 it's
>> Where previously the function would accept the by-value argument, a
>> fatal error is now emitted.
> Not sure about this one. Do you have an example please?
Erm, you do realized that I copied that from the handbook page? Example:
PHP Fatal error: Only variables can be passed by reference in
hi,
On Sun, Jul 25, 2010 at 11:17 AM, Karoly Negyesi wrote:
> Hi,
>
> A mere year after releasing Version 5.3.0 (Version 5.3.0 30-June-2009)
> you are dropping PHP 5.2 support.
We still support 5.2.
There is a huge misunderstanding of "end of active support". It means
that only critical bugs (s
Hi,
A mere year after releasing Version 5.3.0 (Version 5.3.0 30-June-2009)
you are dropping PHP 5.2 support.
This is a very interesting decision as 5.3.0, compatibility wise, is a
major release. I always felt it was PHP 6.0 but it was not called so
because there was a development branched called
14 matches
Mail list logo