Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35663
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 216.239.58.185 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=Bx6qaWU2nSbnQ2N69ZltjlMtcKcbnCyFNQqO6WJrzcFAPg6Lxaj3AYy8L46w5dmK0gBOEsApM4uERYNfcvLytY7cRCGC3YiUpfEDsb78zgrfC+t0IVqV319LC8GdmHTlmxLlPk1n01YAUUHxRPZcsyNPwsNlnZjtN6wdlVVARJw=
Message-ID: <1e12984d0802201243gfa51f01i311891e8965ed51e@mail.gmail.com>
Date: Wed, 20 Feb 2008 21:43:28 +0100
Reply-To: php@stefan-marr.de
Sender: stefan.marr.de@gmail.com
To: "Marcus Boerger" <helly@php.net>
Cc: Evert|Rooftop <evert@rooftopsolutions.nl>, 
	"Stanislav Malyshev" <stas@zend.com>, internals@lists.php.net
In-Reply-To: <1495054633.20080220205951@marcus-boerger.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <001c01c87264$3c01b4e0$b4051ea0$@de>
	 <173732199.20080219175837@marcus-boerger.de>
	 <1203452909.24580.9.camel@localhost>
	 <1e12984d0802191323o710c6b8ej3a54af7901cf35f1@mail.gmail.com>
	 <47BB4AC9.9070701@zend.com>
	 <1e12984d0802191346x7c145d7fp14c01ec4e5993779@mail.gmail.com>
	 <47BB4F49.1030904@rooftopsolutions.nl>
	 <1e12984d0802191359p4f21c3acrdff4b86adfb4bf3@mail.gmail.com>
	 <1495054633.20080220205951@marcus-boerger.de>
Subject: Re: [PHP-DEV] RFC: Traits for PHP
From: php@stefan-marr.de ("Stefan Marr")

> If we feel it gets necessary we probbaly
> might want to support a syntax like:
>  'trait_method' => false
>  'trait_method' => 'new_name'
>  'trait_method' => array('new_name', 'trait_method'
I'm not comfortable with this notation, since it strengthens the
impression that it is renaming.

In my eyes it looks like this:

"trait_method => false" means trait_method is moved to false, it is
deleted, but this leads to the wrong impression of this:
"trait_method => new_name" means trait_method is moved to new_name,
and I am absolutely against this notion.

Renaming implies in my opinion all references to this method might be
adjusted (what is not possible at all) and the original method is
"lost".
There are several problems with with "lost" method already discussed
on this list, like not fulfilled requirements (the delete method
thing).

The aliasing notion has the benefit that a method has to be explicitly
excluded to be removed. So the developer explicitly requests for a
change that he will handle on its own.

Kind Regards
Stefan