Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79227
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54771C61.5040507@gmail.com>
References: <CAFp73XvRNoDF5N1-H4+YBSB3G2_OBAM3+x6Tu3beT5-H9O+deg@mail.gmail.com>
	<CAMyk_AYuOz7cQsU1VT4F_1nScQ1XWTJend6pTFu9o0Y8E_XL3g@mail.gmail.com>
	<54771C61.5040507@gmail.com>
Date: Thu, 27 Nov 2014 14:10:02 +0100
Message-ID: <CAH-PCH4r9ub2t=2Tt9pqSmzZV6OnLaXARfxSisqgtFew7eW8Qw@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113cd1f0b542040508d6dca6
Subject: Re: [PHP-DEV] [RFC] Abstract final classes
From: tyra3l@gmail.com (Ferenc Kovacs)

--001a113cd1f0b542040508d6dca6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Nov 27, 2014 at 1:43 PM, Rowan Collins <rowan.collins@gmail.com>
wrote:

> Lazare Inepologlou wrote on 27/11/2014 10:35:
>
>  2014-11-27 4:47 GMT+01:00 guilhermeblanco@gmail.com <
>> guilhermeblanco@gmail.com>:
>>
>>  Hi,
>>>
>>> I worked on an implementation of a somehow controversial concept that
>>> exists in hack and C#: abstract final classes.
>>>
>>> https://wiki.php.net/rfc/abstract_final_class
>>>
>>> My motivation is to further expand class support to add modifiers (PPP =
-
>>> public, protected, private). I added this change to initially segregate
>>> grammar rules. It was an easy feature without extensive complexity and
>>> covers some use-cases.
>>>
>>>
>>>  "Abstract final" is a strange way to name it. What you want is a
>> "static"
>> class:
>>
>> * The fact that one cannot initialise an abstract class is only a side
>> effect. Abstract classes are meant to be used for inheritance.
>>
>> * Abstract static methods are not possible (one more reason why abstract
>> is
>> a bad name).
>>
>> * A "static" class does not have to be final, given the fact that PHP is
>> one of the few languages that offer a robust Late Static Binding.
>>
>
> This has always been my feeling. To me, "abstract" means "must be
> extended", and "final" means "can't be extended", so combining the two
> seems like a self-contradiction.
>
> The fact that abstract classes allow static methods to be called without
> sub-classing always seems a bit odd to me - it's as though only the
> constructor is really abstract, not the whole class.
>
> A "static" class, however, whether "final" or not, is definitely somethin=
g
> I've wanted.
>
> Regards,
> --
> Rowan Collins
> [IMSoP]
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
for the record I also brought up this argument (abstract and final being
contradicting ideas) in the pull request comments(before this thread was
created).

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--001a113cd1f0b542040508d6dca6--