Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17597 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88267 invoked by uid 1010); 8 Aug 2005 12:53:59 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 88252 invoked from network); 8 Aug 2005 12:53:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Aug 2005 12:53:59 -0000 X-Host-Fingerprint: 80.237.204.20 ds80-237-204-20.dedicated.hosteurope.de Linux 2.5 (sometimes 2.4) (4) Received: from ([80.237.204.20:36862] helo=fs1.fairscale.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 1A/F9-04646-6E557F24 for ; Mon, 08 Aug 2005 08:53:58 -0400 Received: from [127.0.0.1] (helo=www.fairscale.de) by fs1.fairscale.de with esmtpa (Exim 4.50) id 1E26yi-00067o-UU; Mon, 08 Aug 2005 14:43:40 +0200 Received: from 83adc50a.funky.uni-osnabrueck.de ([131.173.197.10]) (SquirrelMail authenticated user ic1_80p1); by www.fairscale.de with HTTP; Mon, 8 Aug 2005 14:43:40 +0200 (CEST) Message-ID: <43033.131.173.197.10.1123505020.squirrel@131.173.197.10> In-Reply-To: <42F64DC8.2000205@prohost.org> References: <42F64DC8.2000205@prohost.org> Date: Mon, 8 Aug 2005 14:43:40 +0200 (CEST) To: "Ilia Alshanetsky" Cc: internals@lists.php.net User-Agent: SquirrelMail/1.5.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Subject: Re: [PHP-DEV] Property Overloading RFC From: ml@lalamuhkuh.de ("Roland Tapken") Hi! Sorry for wrong threading or if this solution was suggested before... i currently don't have access to my mail client:) > 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. greets, Roland