On Jan 17, 2015 5:58 PM, "Tony Marston" <tonymars...@hotmail.com> wrote:
"Stelian Mocanita" wrote in message
news:camc0ws5lpdvqf_5p8uiwbzuqc+max+shmmi8pzlggrfoj7a...@mail.gmail.com...
Florian Margaine wrote on 16/01/2015 13:01:
Hi Stelian,
Stelian Mocanita writes:
Not under active development doesn't mean that the application
shouldn't
be able to upgrade PHP and enjoy the bug/security fixes or performance
improvements that new versions provide.
I agree. If the core developers want each new release, with its bug fixes
and security enhancements, to be adopted by the community then they
should
stop breaking BC for no good reason.
Can wie stop using this argument pls?
Not while it is a valid argument in the eyes of the millions of developers
who use PHP
We are talking about something deprecated since 10 years, about the 1st
major release in a decade, something we will use for the next 12-14 years.
That is the point - PHP 4 constructors have NOT been marked as deprecated in
the manual, and they produce no warnings at runtime.
If they have not been marked as deprecated then you cannot suddenly remove
them.
5.x will be maintained as well for the next 3 years (plus distros LTS). We
do not break BC since quite some time too in minor releases.
Good. Breaking BC for no good reason is never a good idea.
Cheers,
Pierre
--
Tony Marston
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
