Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42679 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71094 invoked from network); 17 Jan 2009 20:29:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Jan 2009 20:29:23 -0000 Authentication-Results: pb1.pair.com header.from=helly@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=helly@php.net; spf=unknown; 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:50138] helo=h1149922.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EC/36-41390-3AF32794 for ; Sat, 17 Jan 2009 15:29:23 -0500 Received: from MBOERGER-ZRH.corp.google.com (203-16.203-62.cust.bluewin.ch [62.203.16.203]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by h1149922.serverkompetenz.net (Postfix) with ESMTP id 1805211F3CD; Sat, 17 Jan 2009 21:29:20 +0100 (CET) Date: Sat, 17 Jan 2009 21:26:30 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <1956503865.20090117212630@marcus-boerger.de> To: Stanislav Malyshev CC: Ionut Gabriel Stan , Marcus Boerger , In-Reply-To: <496E12CE.2080403@zend.com> References: <1016989528.20090112233204@marcus-boerger.de> <496BCD33.4080703@zend.com> <133861245.20090113225847@marcus-boerger.de> <496D2074.3070303@zend.com> <496DD269.4050701@gmail.com> <496E12CE.2080403@zend.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] prototyping From: helly@php.net (Marcus Boerger) Hello Stanislav, Wednesday, January 14, 2009, 5:29:02 PM, you wrote: > Hi! >> That is one example of convoluted code that is already possible. If a >> developer creates such a mess is his fault. > "Convoluted"? "Mess"? Are you kidding me? It's standard usage of access > handlers. It is a mess right now. You assign a closure to another method and get access to the original owners private members. That is not only unexpected and contradicting anything that any oyther language ever but but also violates our very own basic ideas. That is what I call a mess. Best regards, Marcus