Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:4902 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 64763 invoked by uid 1010); 21 Oct 2003 00:42:00 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 64739 invoked by uid 1007); 21 Oct 2003 00:42:00 -0000 Message-ID: <20031021004200.64738.qmail@pb1.pair.com> To: internals@lists.php.net Reply-To: "l0t3k" References: <5.1.0.14.2.20031016174936.02ffdc98@127.0.0.1> Date: Mon, 20 Oct 2003 20:41:21 -0400 Lines: 41 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Posted-By: 68.211.116.70 Subject: Re: PHP 5 Beta 2 From: cshmoove@bellsouth.net ("l0t3k") Andi, is/was someone planning on looking into the problem of class constants for internal classes? i'll include a comment (from Moriyoshi) in our project as a reference /* * XXX: zend_initialize_class_data() is totally mess! because it * virtually doesn't take it into account that the constants of * internal classes are persistently allocated while they will actually * be destroyed by the normal ZVAL_PTR_DTOR() which accepts zvals * allocated by emalloc(). * That's why I prepared my own zval destructors. But this workaround is * not safe yet because all the symbols bound dynamically by the Zend engine * are supposed to be released before the destruction of class entries * registered by extensions at the engine shutdown. * So this extension has to be linked statically to the PHP runtime for now. * .. :( */ that's the only outstanding issue i have personally with the beta. otherwise the current CVS works well. ive tested the new read/write dimension hooks, object level iterators, as well as casting, and they work as expected. l0t3k "Andi Gutmans" wrote in message news:5.1.0.14.2.20031016174936.02ffdc98@127.0.0.1... > Hey, > > I'd like to release Beta 2 at the end of the week after next (30th of > October). Please make sure your code is ready by then. If there's anything > critical that can't be ready on time please let me know (although I doubt > there is such a thing). > Beta 2 will be a big step forward from beta 1 and I think once it's out > it'll allow us to build the necessary momentum for releasing beta's of PHP > 5 more often. > > Andi