Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79353
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <C3F2BD8F-6E5E-4FED-B5AF-5C535C22D45A@strojny.net>
References: <003c01d00d6e$f4fd77c0$def86740$@tutteli.ch> <C3F2BD8F-6E5E-4FED-B5AF-5C535C22D45A@strojny.net>
Date: Mon, 1 Dec 2014 14:46:28 -0500
Message-ID: <CAFp73Xv7fjDYtZUrndM7o6cceKyyNk6h4rih5N5TDC8GSKwCKQ@mail.gmail.com>
To: Lars Strojny <lars@strojny.net>
Cc: Robert Stoll <php@tutteli.ch>, internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113ebbf81d886d05092cdfed
Subject: Re: [PHP-DEV] [RFC] Static classes (Was Abstract final classes)
From: guilhermeblanco@gmail.com ("guilhermeblanco@gmail.com")

--001a113ebbf81d886d05092cdfed
Content-Type: text/plain; charset=UTF-8

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

--001a113ebbf81d886d05092cdfed--