"Stephen Coakley" wrote in message
news:db.f0.25279.8c0d9...@pb1.pair.com...
On 02/18/2016 06:41 AM, Nikita Popov wrote:
Hi internals!
I've created a bulk-deprecation RFC for PHP 7.1:
https://wiki.php.net/rfc/deprecations_php_7_1
I'm using this RFC to collect various deprecations targeting PHP 7.1, as
having individual RFCs for these is too much management overhead. Each
deprecated feature will get its own vote, of course.
This RFC is incomplete -- I'm posting it now so people can suggest other
things that should be deprecated. I expect it to grow over time and don't
plan to vote on it in the immediate future.
Thanks,
Nikita
My stance on deprecations:
> It seems that perfection is attained not when there is nothing more
> to add, but when there is nothing more to remove.
> - Antoine de Saint Exupéry
I'd say any function that provides duplicate functionality, or encourages
bad practice, should be deprecated. Keeping the standard library clean and
focused is ideal.
But who decides what is "bad" practice and what is not? It is impossible for
ANY language to prevent a bad programmer from writing bad code, so the only
way to prevent bad code 100% would be to have a language that did nothing at
all.
Deprecating something just because you don't like is NOT a good enough
reason.
--
Tony Marston
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
