Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:35612 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11747 invoked by uid 1010); 19 Feb 2008 20:54:19 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 11732 invoked from network); 19 Feb 2008 20:54:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Feb 2008 20:54:19 -0000 Authentication-Results: pb1.pair.com header.from=jochem@iamjochem.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=jochem@iamjochem.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain iamjochem.com from 194.109.193.121 cause and error) X-PHP-List-Original-Sender: jochem@iamjochem.com X-Host-Fingerprint: 194.109.193.121 mx1.moulin.nl Linux 2.6 Received: from [194.109.193.121] ([194.109.193.121:52333] helo=mx1.moulin.nl) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0E/87-55225-AF14BB74 for ; Tue, 19 Feb 2008 15:54:19 -0500 Received: from localhost (localhost [127.0.0.1]) by mx1.moulin.nl (Postfix) with ESMTP id 8955B27E02A; Tue, 19 Feb 2008 21:54:15 +0100 (CET) X-Virus-Scanned: amavisd-new at moulin.nl Received: from mx1.moulin.nl ([127.0.0.1]) by localhost (mx1.moulin.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JoV7CkOy9c8k; Tue, 19 Feb 2008 21:54:10 +0100 (CET) Received: from [10.0.13.105] (ip129-15-211-87.adsl2.versatel.nl [87.211.15.129]) by mx1.moulin.nl (Postfix) with ESMTP id C54F227E152; Tue, 19 Feb 2008 21:54:09 +0100 (CET) Message-ID: <47BB41F1.40607@iamjochem.com> Date: Tue, 19 Feb 2008 21:54:09 +0100 User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Marcus Boerger CC: Lars Strojny , php@stefan-marr.de, internals Mailing List References: <001c01c87264$3c01b4e0$b4051ea0$@de> <1203453089.24580.12.camel@localhost> <1615703844.20080219214224@marcus-boerger.de> In-Reply-To: <1615703844.20080219214224@marcus-boerger.de> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RFC: Traits for PHP From: jochem@iamjochem.com (Jochem Maas) firstly, I'd like to reiterate the general sentiment that Stefans RFC is blinding! (that's a good thing in this context ;-) Marcus Boerger schreef: > Hello Lars, > > we could even go for include here if we wanted to avoid use as much as > adding a new keyword. Personally I don't mind using keywords for different > stuff as long as it cannot conflict. That is in this case true for both > include and use. how about 'possesses' or 'exhibits' - both these words are closer to the natural language usage of 'trait' with regard to a subject. John exhibits a **** trait Jack possesses a **** trait a person coming accross 'use' or 'include' in the context of trait attribution may either make assumptions or become confused as to possible changes/additions to the use and/or include functionality, a new keyword that aptly describes the intention will more likely force users to actually find out what it means. an another alternative might be 'applies' - which doesn't fit the natural language usage of 'trait' but does succintly describe what is happening. just a thought. > > marcus > > Tuesday, February 19, 2008, 9:31:29 PM, you wrote: > >> Hi Stefan, > >> Am Montag, den 18.02.2008, 20:27 +0100 schrieb php@stefan-marr.de: >> [...] >>> class ezcReflectionMethod extends ReflectionMethod { >>> use ezcReflectionReturnInfo; >>> /* ... */ >>> } > >> I'm not sure if the use-keyword is a good idea as namespaces are already >> "used". If we use "use" for traits, maybe going back to "import" for >> namespaces would be the way to go. > >> cu, Lars > > > > Best regards, > Marcus >