Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:35654 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16654 invoked by uid 1010); 20 Feb 2008 20:01:29 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 16639 invoked from network); 20 Feb 2008 20:01:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Feb 2008 20:01:29 -0000 Authentication-Results: pb1.pair.com smtp.mail=helly@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=helly@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.94.56 as permitted sender) X-PHP-List-Original-Sender: helly@php.net X-Host-Fingerprint: 85.214.94.56 aixcept.net Linux 2.6 Received: from [85.214.94.56] ([85.214.94.56:38738] helo=h1149922.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 98/62-30965-8178CB74 for ; Wed, 20 Feb 2008 15:01:28 -0500 Received: from dhcp-172-28-202-237.zrh.corp.google.com (unknown [193.142.125.1]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by h1149922.serverkompetenz.net (Postfix) with ESMTP id DACDE1B3656; Wed, 20 Feb 2008 21:01:25 +0100 (CET) Date: Wed, 20 Feb 2008 21:01:27 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <1016146449.20080220210127@marcus-boerger.de> To: Jochem Maas CC: Lars Strojny , php@stefan-marr.de, internals Mailing List In-Reply-To: <47BB41F1.40607@iamjochem.com> References: <001c01c87264$3c01b4e0$b4051ea0$@de> <1203453089.24580.12.camel@localhost> <1615703844.20080219214224@marcus-boerger.de> <47BB41F1.40607@iamjochem.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RFC: Traits for PHP From: helly@php.net (Marcus Boerger) Hello Jochem, good arguments. And good ideas. I'd favor 'posesses' then. marcus Tuesday, February 19, 2008, 9:54:09 PM, you wrote: > 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 >> Best regards, Marcus