Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:51207 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95914 invoked from network); 3 Jan 2011 09:16:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Jan 2011 09:16:35 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@stefan-marr.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=php@stefan-marr.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain stefan-marr.de from 81.20.134.149 cause and error) X-PHP-List-Original-Sender: php@stefan-marr.de X-Host-Fingerprint: 81.20.134.149 vps-1012701-4512.united-hoster.de Received: from [81.20.134.149] ([81.20.134.149:33775] helo=vps-1012701-4512.united-hoster.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5F/41-20041-2F3912D4 for ; Mon, 03 Jan 2011 04:16:34 -0500 Received: from 94-224-217-64.access.telenet.be ([94.224.217.64] helo=[192.168.0.13]) by vps-1012701-4512.united-hoster.de with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1PZgWl-0003h5-85; Mon, 03 Jan 2011 10:16:31 +0100 Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii In-Reply-To: <4D219123.2080803@yahoo.com.au> Date: Mon, 3 Jan 2011 10:16:25 +0100 Cc: internals@lists.php.net Content-Transfer-Encoding: quoted-printable Message-ID: <9F94CB7F-AEC1-4E54-B4E5-29C3E55DCACA@stefan-marr.de> References: <89C52156-CF92-4DDB-8BA4-4ABF6883512C@stefan-marr.de> <4D21415A.10002@gmail.com> <4D21658A.2030208@yahoo.com.au> <4D219123.2080803@yahoo.com.au> To: Ben Schmidt X-Mailer: Apple Mail (2.1082) Subject: Re: [PHP-DEV] Traits and Properties From: php@stefan-marr.de (Stefan Marr) Hi Ben: On 03 Jan 2011, at 10:04, Ben Schmidt wrote: > In this email thread you seemed to be saying that properties defined = in > traits are completely ignored, but in the RFC and svn it seems to be > saying that properties in traits are not ignored, but are merged into > the class and/or trigger errors/warnings. So, which is it? Ignored or > not? Or is some aspect of them ignored and some aspect not? The RFC was discussed on this list, and the RFC should explain what the = current state of the implementation is. So, the RFC and the = implementation are the specifications. In case they differ it has to be = fixed. With regard to state, from my academic point of view, it is not handled, = however, the language should be now in a shape which provides my = interpretation of 'expected behavior' with regard to property = definitions. When they collide, you get a notice, but the language does not help you = in solving the problem. Best regards Stefan --=20 Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525