"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.
Completely agree, but you get once in N years a chance to do some cleanup
on the language. If people expect no BC breaks on major versions, when is
the time for the cleanup?
It is one thing to remove functionality from the core if it a security issue
or it causes bugs, but people's definitions of "clean" are many and varied,
so using that as an excuse to break the language will not down well with
those millions of website owners whose applications suddenly stop working
after an upgrade.
By "clean" it is obvious that you mean "style" as in "don't do it like that,
do it like this". It is not up to the core developers to dictate style on
the rest of the programmer community - you provide the basic tools, and it
is up to the individual programmer to decide what functions to use in order
to solve the problem at hand. Programming style is the prerogative of the
individual programmer, or a team of programmers, and should never be
dictated by any outside agency.
That's one thing. The other thing is that there's a flow in your logic. If
you want the bug/security/performance fixes, it means you are already
running latest stable and for some reason you completely ignored all of the
deprecation warnings until now. I think we can both agree on this being a
bit far-fetched.
I am using PHP 5.6.4 with error_reporting=E_ALL and I am not seeing any
messages regarding my use of PHP 4 constructors. They are also NOT marked as
deprecated in the manual.
If they are not marked as deprecated then you cannot suddenly remove them.
Besides, what problem(s) would be solved by removing PHP 4 constructors? If
there are no problems then removing them would not only NOT solve any
problem it would actually create a HUGE problem for all those applications
which still use them.
Not to mention that all the old ctor fatal errors can be fixed with an
automated scripts that replaces the old ctors with the new ones.
Stelian
--
Tony Marston
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
