Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:45823 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 5777 invoked from network); 15 Oct 2009 14:20:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Oct 2009 14:20:05 -0000 Authentication-Results: pb1.pair.com header.from=php@stefan-marr.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=php@stefan-marr.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain stefan-marr.de from 85.88.12.247 cause and error) X-PHP-List-Original-Sender: php@stefan-marr.de X-Host-Fingerprint: 85.88.12.247 toolslave.net Received: from [85.88.12.247] ([85.88.12.247:35440] helo=uhweb12247.united-hoster.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E4/74-14330-19F27DA4 for ; Thu, 15 Oct 2009 10:20:02 -0400 Received: from soft83.vub.ac.be ([134.184.43.183]) by uhweb12247.united-hoster.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from ) id 1MyRBH-0005kx-24; Thu, 15 Oct 2009 16:19:55 +0200 Mime-Version: 1.0 (Apple Message framework v1074) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes In-Reply-To: <4AD62E77.9010802@zend.com> Date: Thu, 15 Oct 2009 16:19:46 +0200 Cc: Lukas Kahwe Smith , internals@lists.php.net Content-Transfer-Encoding: 7bit Message-ID: References: <002b01c92d67$ae92fdc0$0bb8f940$@de> <9D1CD88B-3A75-453C-9515-5F31E60F90AC@pooteeweet.org> <90CF2907-8C30-4EB0-9AC5-AD00EFC14023@stefan-marr.de> <4AD62E77.9010802@zend.com> To: Stanislav Malyshev X-Mailer: Apple Mail (2.1074) Subject: Re: [PHP-DEV] Request for Comments: Horizontal Reuse for PHP From: php@stefan-marr.de (Stefan Marr) > I thought before merging code it would be useful to have some > discussion on if the code is actually doing what we want. If it's > based on http://wiki.php.net/rfc/horizontalreuse then for example I > can see some potential issues for bytecode caching related to > renaming and changing visibility. Sure, the discussion will be necessary to fix the final design of the remaining rough edges like choice of keywords. The current state of the code is basically documented by the test case. They cover all syntactical features and their implications for using traits. However, this functionality is covered by the Traits part of the RFC as well. > Also, it is not clear that we want grafts there at all, some aspects > of them seem to get too hairy, esp. $this issue or statics. Personally, I see question of Traits or Grafts as an exclusive one. It would not do any good to have both of them. And, grafts have not been implemented. Best regards Stefan > -- > Stanislav Malyshev, Zend Software Architect > stas@zend.com http://www.zend.com/ > (408)253-8829 MSN: stas@zend.com > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > -- Stefan Marr Software Languages Lab Former Programming Technology Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://prog.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525