Hi George,
Iiuc, the problem you're trying to solve is that PHP offers too many
ways to do the same thing and if there were fewer then PHP code would be
easier to write, read and maintain.
Differences in code that make no difference to the compiler are
differences in style.
The conventional solution is to adopt a style spec and use a linter.
I've experienced this in Ruby, JS and PHP and it's effective.
This conventional solution causes a lot less breakage than attempting to
mitigate the problem by changing the language.
It's annoying enough to have to deal with the promulgation of a new
style spec and corresponding linter in your organization. Imagine if
such a change were to be promulgated by The Rulers of PHP.
Tom
- Re: [PHP-DEV] Deprecation ideas for PHP 8 Tom Worster
