Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63975
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <58826104.Pqfe10HgIT@rofl>
References: <508A67E6.2000405@zerocue.com>
	<50A39C58.6030501@zerocue.com>
	<CAF+90c_jVmHk_ZXc1GXNwwiZ3Zy8oubmW8gudbmi7qppH68p2A@mail.gmail.com>
	<58826104.Pqfe10HgIT@rofl>
Date: Mon, 19 Nov 2012 16:41:43 +0100
Message-ID: <CAF+90c_gQrisWQUcCBmjvPdfyLhykKyyJeWKySA2UvfaJyv=Pg@mail.gmail.com>
To: Patrick Schaaf <php@bof.de>
Cc: PHP internals <internals@lists.php.net>, Clint Priest <cpriest@zerocue.com>
Content-Type: multipart/alternative; boundary=485b390f7f764ba7ab04cedaf43c
Subject: Re: [PHP-DEV] [RFC] Property Accessors v1.2 : Internal Accessor
 Method Visibility / Callability
From: nikita.ppv@gmail.com (Nikita Popov)

--485b390f7f764ba7ab04cedaf43c
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Nov 14, 2012 at 5:24 PM, Patrick Schaaf <php@bof.de> wrote:

> I thought I'd made a proposal that would solve that problem, but maybe it
> was
> overlooked, or more likely too ugly to be recognized as such.
>
> Requires a single new feature / syntax, that at least I find missing right
> now:
>
> class ... {
>   no methodname();
>    // or
>   no $property;
> }
>
> removing the specified thing from the class, with the possibility to then
> redefine it. Silently ignore this when the thing doesn't exist.
>

Removing methods from an extending class is an LSP violation. It shouldn't
be done and I don't know any languages with an object orientation system
similar to PHP that allow this.

I think that this "no" tagging approach wouldn't really solve anything,
just patch it up in some rather ugly way.

Nikita

--485b390f7f764ba7ab04cedaf43c--