Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17598 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 89971 invoked by uid 1010); 8 Aug 2005 12:55:41 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 89956 invoked from network); 8 Aug 2005 12:55:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Aug 2005 12:55:41 -0000 X-Host-Fingerprint: 82.94.239.5 jdi.jdi-ict.nl Linux 2.5 (sometimes 2.4) (4) Received: from ([82.94.239.5:45573] helo=jdi.jdi-ict.nl) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 1D/3A-04646-C4657F24 for ; Mon, 08 Aug 2005 08:55:40 -0400 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.12.11/8.12.11) with ESMTP id j78Ctbmo012164 for ; Mon, 8 Aug 2005 14:55:37 +0200 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.12.11/8.12.11) with ESMTP id j78CtWjL012139; Mon, 8 Aug 2005 14:55:33 +0200 Date: Mon, 8 Aug 2005 14:55:32 +0200 (CEST) X-X-Sender: derick@localhost To: Roland Tapken cc: Ilia Alshanetsky , internals@lists.php.net In-Reply-To: <43033.131.173.197.10.1123505020.squirrel@131.173.197.10> Message-ID: References: <42F64DC8.2000205@prohost.org> <43033.131.173.197.10.1123505020.squirrel@131.173.197.10> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at jdi-ict.nl Subject: Re: [PHP-DEV] Property Overloading RFC From: derick@php.net (Derick Rethans) On Mon, 8 Aug 2005, Roland Tapken wrote: > > 3. There is no way for the magic methods to return a meaningfull error > > when a property doesn't "exist". Of course it is possible to throw an > > error with "trigger_error" or "throw" in case a property doesn't "exist" > > in a specific class, but the file and line numbers would not match the > > actually get/set action. debug_backtrace() can be used to retrieve the > > correct file and line, but as you have to do this for every class where > > you want to use setters and > > getters *and* you have to implement your own error message rendering > > function this is not really a suitable option either. > > Don't know if this can be implemented... but what's about a 3rd boolean > "handled" call-by-reference-parameter which must be switched to "TRUE" if > the property could be handled? Should be TRUE if ommitted for bc reasons, > of course. That was my original idea. Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org