Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17528 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67231 invoked by uid 1010); 4 Aug 2005 08:22:16 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 67216 invoked from network); 4 Aug 2005 08:22:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Aug 2005 08:22:16 -0000 X-Host-Fingerprint: 212.112.227.169 ipx11223.ipxserver.de Linux 2.4/2.6 Received: from ([212.112.227.169:35804] helo=ipx11223.ipxserver.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 1C/65-04646-730D1F24 for ; Thu, 04 Aug 2005 04:22:16 -0400 Received: from localhost (localhost [127.0.0.1]) by ipx11223.ipxserver.de (Postfix) with ESMTP id 106BADF00C0; Thu, 4 Aug 2005 10:22:33 +0200 (CEST) Received: from ipx11223.ipxserver.de ([127.0.0.1]) by localhost (ipx11223 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26099-04; Thu, 4 Aug 2005 10:22:29 +0200 (CEST) Received: from [127.0.0.1] (i528C1F75.versanet.de [82.140.31.117]) by ipx11223.ipxserver.de (Postfix) with ESMTP id B86D8DF0045; Thu, 4 Aug 2005 10:22:28 +0200 (CEST) Message-ID: <42F1D02C.8050001@php.net> Date: Thu, 04 Aug 2005 10:22:04 +0200 User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derick Rethans Cc: Andrei Zmievski , PHP Developers Mailing List , Jan Borsodi , Raymond Bosman , Frederik Holljen , Tobias Schlitt References: <39FD64FE-3B15-4E66-A4CD-C392B666BD32@gravitonic.com> <42F15B26.6060601@php.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by somedaemon at backendmedia.com Subject: Re: [PHP-DEV] Property Overloading RFC From: lsmith@php.net (Lukas Smith) Derick Rethans wrote: > On Thu, 4 Aug 2005, Lukas Smith wrote: > > >>I wonder if it wouldnt be enough to be able to force the triggering of >>__set(), __get() for all properties be enough to deal with your situation? > > > No, besides that would break BC, it would also not solve the problem of > returning errors correctly. I said "be able to" and not that this should become the norm. So you would be able to flag an object to behave in this way. Heck this flag could be "allow now virtual properties, and trigger __set()/__get() always and throw the proper error otherwise". regards, Lukas