Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:28067 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55332 invoked by uid 1010); 19 Feb 2007 10:19:09 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 55317 invoked from network); 19 Feb 2007 10:19:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Feb 2007 10:19:09 -0000 X-Host-Fingerprint: 80.123.98.46 unknown Received: from [80.123.98.46] ([80.123.98.46:4751] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 51/D0-01477-A9979D54 for ; Mon, 19 Feb 2007 05:19:07 -0500 Message-ID: <51.D0.01477.A9979D54@pb1.pair.com> To: internals@lists.php.net Date: Mon, 19 Feb 2007 11:19:10 +0100 User-Agent: Thunderbird 1.5.0.9 (X11/20070103) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Posted-By: 80.123.98.46 Subject: [PROPOSAL] Change (just slightly) read/write_property() and get_property_ptr_ptr() usage From: mike@php.net (Michael Wallner) Hi, I'd like to suggest a change to how the read_property object handler operates. Wouldn't it be reasonable for the engine to use get_property_ptr_ptr() whenever it wants to modify a property and get rid of using read_property() for write access? That would make rather simple ops like concatenation, in-/decrementation etc work again with overloaded internal classes. Just make the engine use read_property() followed by a write_property() when there's no get_property_ptr_ptr(). Punish me if I'm really that far off. Thoughts? -- Michael