Newsgroups: php.internals,php.internals Path: news.php.net Xref: news.php.net php.internals:18554 php.internals:18555 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 53130 invoked by uid 1010); 30 Aug 2005 09:58:23 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 53111 invoked from network); 30 Aug 2005 09:58:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Aug 2005 09:58:23 -0000 X-Host-Fingerprint: 212.183.41.244 M2480P020.adsl.highway.telekom.at Received: from ([212.183.41.244:6892] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 56/77-15098-EBD24134 for ; Tue, 30 Aug 2005 05:58:23 -0400 To: internals@lists.php.net,Dmitry Stogov Message-ID: <43142D1E.3040108@php.net> Date: Tue, 30 Aug 2005 11:55:42 +0200 Organization: IWORKS User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040803 [ http://iworks.at ] X-Accept-Language: de-AT, de-DE, de, en, en-GB, en-US MIME-Version: 1.0 CC: internals@lists.php.net, Andi Gutmans References: <000001c5ad38$c455ac50$e902a8c0@thinkpad> In-Reply-To: <000001c5ad38$c455ac50$e902a8c0@thinkpad> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Posted-By: 212.183.41.244 Subject: Re: Constants and static methods for internal classes From: mike@php.net (Michael Wallner) Hi Dmitry Stogov, you wrote: > The patch is maden for "easiest" usage and it doesn't support internal > array/constants properties (they weren't supported before). So why burden the weigh of allocation, initialization, destruction and freeing on the extension developer? This will force every extension writer to implement a kind of my dup_zval() function, wouldn't it? And as there's not much reference devs will spam the list on how to use static properties right. I think we could avoid this by stretching the minimalistic approach a bit and provide at least a zend_init_static_properties(). Thanks a lot, -- Michael - < mike(@)php.net >