Re: [RFC] Static classes (Was Abstract final classes)
| From: | guilhermeblanco@gmail.com | Date: | Mon, 01 Dec 2014 19:46:28 +0000 |
| Subject: | Re: [RFC] Static classes (Was Abstract final classes) | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-79353@lists.php.net to get a copy of this message | ||
I'm working on a patch right now and I removed the implicit configuration
of static to methods.
It's only missing reflection magic. Should be out of the oven in one hour
or less.
On Mon, Dec 1, 2014 at 2:44 PM, Lars Strojny <lars@strojny.net> wrote:
> Hi Guilherme, hi Robert.
>
> > On 01 Dec 2014, at 14:58, Robert Stoll <php@tutteli.ch> wrote:
> >
> > I am not sure what makes more sense for PHP, but just as
> thought-provoking impulse, wouldn't it be better just to check that all
> methods are static and __construct private instead of turning methods
> magically into static methods and __construct private?
>
> I very much like the RFC in its current state except for the implicit
> static. While we can preserve the behaviour of automatically turning
> methods into static methods, this should indeed trigger a warning.
>
> cu,
> Lars
--
Guilherme Blanco
MSN: guilhermeblanco@hotmail.com
GTalk: guilhermeblanco
Toronto - ON/Canada