Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39228 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30075 invoked from network); 23 Jul 2008 15:40:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jul 2008 15:40:55 -0000 Authentication-Results: pb1.pair.com smtp.mail=php_lists@realplain.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=php_lists@realplain.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain realplain.com from 209.235.152.152 cause and error) X-PHP-List-Original-Sender: php_lists@realplain.com X-Host-Fingerprint: 209.235.152.152 mail962c35.nsolutionszone.com Linux 2.5 (sometimes 2.4) (4) Received: from [209.235.152.152] ([209.235.152.152:46674] helo=mail962c35.nsolutionszone.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0A/75-12534-40157884 for ; Wed, 23 Jul 2008 11:40:53 -0400 X-POP-User: wilmascam.centurytel.net Received: from pc1 (d13-125.rt-bras.pell.centurytel.net [69.179.187.125]) by mail962c35.nsolutionszone.com (8.13.6.20060614/8.13.1) with SMTP id m6NFelri031629; Wed, 23 Jul 2008 15:40:48 GMT Message-ID: <01b801c8ecda$7ae1e770$0201a8c0@pc1> To: , "Lukas Kahwe Smith" References: <161BC537-BBB8-4B73-B573-4BBA080CF743@pooteeweet.org> Date: Wed, 23 Jul 2008 10:40:47 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1914 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914 Subject: Re: [PHP-DEV] 5.3 feature freeze rapidly approaching From: php_lists@realplain.com ("Matt Wilmas") Hi Lukas, all, Don't know if my two Zend-related patches can be used, or how much time there is to add them (after alpha 1...?). Waiting to hear about "No runtime fetching of built-in global constants." And the second, "Some string changes/optimizations," I'm sure it's fine to update the syntax highlighting and remove the duplicate NOWDOC-related things (pretty trivial). Just wondering if the removal of the INIT_STRING opcode is acceptable. Otherwise... 1) As far as any of those re2c issues, *I* don't know about fixing them, and the few extra scanner tweaks/optimizations I said I had in mind can be done anytime. 2) There's a small bug (forever?) with handling of numeric string array keys (of LONG_MAX/LONG_MIN). Simple, will fix next, since you mentioned bugs. 3) The change that was made to the DVAL_TO_LVAL() macro, which I think should be reverted. Will send a follow-up reminder in a minute about that. Finally, there are a couple small things I had in mind for a while to send along sometime for opinions (haven't done any yet): *) Some consistency updates for formatted print (printf) stuff -- userland function and internal. Been a long time since I looked at any of it, so not sure about specifics! *) A small heredoc syntax addition after seeing an old feature request. *) Fix for old behavior/bug with preg_replace() and /e modifier where it causes weird escaping of quotes. Though this could mess up people that are using their own workaround as I would have, unless it's a flag/option. I know it may be too late for these things :*/, but just wanted to mention them, and I'd still send them to the list if done... I wouldn't consider them major or dangerous. Thanks Johannes and Lukas! - Matt ----- Original Message ----- From: "Lukas Kahwe Smith" Sent: Wednesday, July 23, 2008 > Hi, > > This is just a reminder from your friendly co-RMs that the PHP 5.3 > feature freeze is rapidly approaching: > http://wiki.php.net/todo/php53 > > As you can see there are still a bunch of open topics. For the very > important ones we have tried to contact the authors and work out a > schedule to get them done. If there is anything missing on this list > please make sure to let us know _ASAP_ (or forever hold your peace). > > Please try to get your items done today or over the course of tomorrow > (we are not giving a specific timezone, but try for sooner rather than > later ..). Once we have reached the 25th, we will start being a bit > more strict, so again please make sure we know about the things you > want to do (this includes bug fixes - which we might deem feature > changes) so that things will go smoothly for an alpha1 on the 31st. > > Thank you all for the work that has been done in the past weeks. > Things are shaping up nicely. My main worry point atm is that we are > not sure about the status of re2c. > > regards, > Johannes and Lukas