Re: RFC: Making T_FUNCTION optional in method declarations

From: Date: Sun, 28 Nov 2010 15:04:33 +0000
Subject: Re: RFC: Making T_FUNCTION optional in method declarations
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-50656@lists.php.net to get a copy of this message
From what I understand T_FUNCTION would be optional, rather than removed altogether, is this the case? This would allow those who want to use it the option of using it and would not break existing code. -- Ross Masters <ross@php.net> http://rossmasters.com/ 2010/11/28 David Otton <phpmail@jawbone.freeserve.co.uk> > 2010/11/27 Johannes Schlüter <johannes@schlueters.de>: > > > Without T_FUNCTION token. In my opinion an access modifier /public, > > private protected, static, final) should still be required for keeping > > readability. > > As a plea on behalf of maintenance coders dealing with large, messy > codebases, please, please don't impact our ability to run 'grep -rs > "function functionName" *', or hit F8, or whatever your IDE's > equivalent is. > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >

« previous php.internals (#50656) next »