Re: RFC: Making T_FUNCTION optional in method declarations
| From: | larry@garfieldtech.com | Date: | Thu, 02 Dec 2010 16:07:52 +0000 |
| Subject: | Re: RFC: Making T_FUNCTION optional in method declarations | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-50825@lists.php.net to get a copy of this message | ||
On 12/2/10 7:51 AM, Patrick ALLAERT wrote:
I am still firmly -1 on removing T_FUNCTION for methods.+1 for removing T_VAR and making T_FUNCTION optional in a major release. -1 otherwise.
Correct me if I'm wrong, but isn't T_VAR on class members already an E_STRICT warning? I thought it was... --Larry GarfieldIf people migrate to a major version of PHP> 5 they should at least stop relying on PHP 4 features still valid thanks to BC consideration.-- Patrick Allaert --- http://code.google.com/p/peclapm/ - Alternative PHP Monitor -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.phpAn entire major version relied on the usage of T_VAR within classes. Many people still use it today. I therefore am strongly against removing T_VAR, considering it would break huge amounts of userland code.In either case, it should be deprecated with an E_DEPRECATED warning during at least another major before it gets removed.This makes much sense!