Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:51060 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95282 invoked from network); 16 Dec 2010 17:49:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Dec 2010 17:49:09 -0000 X-Host-Fingerprint: 65.19.76.48 unknown Date: Thu, 16 Dec 2010 12:49:07 -0500 Received: from [65.19.76.48] ([65.19.76.48:2294] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 49/51-19331-2115A0D4 for ; Thu, 16 Dec 2010 12:49:07 -0500 Message-ID: <49.51.19331.2115A0D4@pb1.pair.com> To: internals@lists.php.net References: <89C52156-CF92-4DDB-8BA4-4ABF6883512C@stefan-marr.de> <581ACCE6-71A4-444F-A226-8D87E1B43EEF@stefan-marr.de> User-Agent: slrn/pre1.0.0-18 (Linux) X-Posted-By: 65.19.76.48 Subject: Re: [PHP-DEV] Traits and Properties From: weierophinney@php.net (Matthew Weier O'Phinney) On 2010-12-16, Stefan Marr wrote: > From my point of view the right thing to do with regard to properties > is defined in the test cases below. > > The rational behind providing this semantics is based on the fact that > PHP allows to define properties dynamically anyway, so there is no way > around properties. However, there should be a way that a developer > can notice that the code might not behave as expected in the composed > class. +1 The test cases you include are exactly how I would expect traits to work with regards to properties. -- Matthew Weier O'Phinney Project Lead | matthew@zend.com Zend Framework | http://framework.zend.com/ PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc