Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35727
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 38.99.98.18 cause and error)
Message-ID: <47BEE001.9080602@chiaraquartet.net>
Date: Fri, 22 Feb 2008 08:45:21 -0600
User-Agent: Thunderbird 2.0.0.6 (X11/20071022)
MIME-Version: 1.0
To: Marcus Boerger <helly@php.net>
CC: Lukas Kahwe Smith <mls@pooteeweet.org>, php@stefan-marr.de, 
 Evert|Rooftop <evert@rooftopsolutions.nl>,
 Stanislav Malyshev <stas@zend.com>, internals@lists.php.net
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> <1e12984d0802201243gfa51f01i311891e8965ed51e@mail.gmail.com> <9EE7F229-0710-48E8-9A26-DC8031AF8979@pooteeweet.org> <1985981545.20080222134413@marcus-boerger.de>
In-Reply-To: <1985981545.20080222134413@marcus-boerger.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: Traits for PHP
From: greg@chiaraquartet.net (Gregory Beaver)

Marcus Boerger wrote:
> Hello Lukas,
> 
>   alright,
> 
>    'foo as bar' is ok to me and does not even add a new keyword.
> Ignore or any more keywords are bad and I also think that the correct
> would be hide(ing). But as I further more explained it should really be
> something that only marks a method as private if at all. That can be
> done as:
>    'foo as private' since private is a keyword it cannot conflice anyway.

I like this solution.

I have been uncomfortable with the current trait suggestions because
they occur in the body of the class, whereas extends/implements is
outside.  I think there is a way to handle this, however.

class Blah extends ... implements ... traits trait1, trait2, trait3 {
}

The above presents a problem if trait2 contains conflicting method
names, but a simple way to solve it would be to automatically alias
methods by prepending traitname::

<?php

trait trait1 { function a(){}}
trait trait2 { function a(){}}
class Blah extends ... implements ... traits trait1, trait2, trait3 {
}
?>

would create method "trait2::a" and we can alias it in the class body.

Also, $a->{'trait2::a'}(); is legal syntax, so no problems there.


Example:

<?php

trait trait1 { function a(){}}
trait trait2 { function a(){}}
class Blah extends ... implements ... traits trait1, trait2, trait3 {
    function trait2::a as b;
}
?>

This would be 100% obvious to me, and far clearer for reading since we
would be explicitly saying we're aliasing a function.

So, I rescind my previous syntax suggestion in favor of the above.

Greg