Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:43638 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37442 invoked from network); 6 Apr 2009 17:15:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Apr 2009 17:15:59 -0000 Authentication-Results: pb1.pair.com smtp.mail=shire@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=shire@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 208.43.138.18 as permitted sender) X-PHP-List-Original-Sender: shire@php.net X-Host-Fingerprint: 208.43.138.18 sizzo.org Linux 2.6 Received: from [208.43.138.18] ([208.43.138.18:34489] helo=sizzo.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4A/ED-02528-FC83AD94 for ; Mon, 06 Apr 2009 13:15:59 -0400 Received: from 173-116-137-60.pools.spcsdns.net (173-116-137-60.pools.spcsdns.net [173.116.137.60]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by sizzo.org (Postfix) with ESMTPSA id 44064CBE482; Mon, 6 Apr 2009 10:15:55 -0700 (PDT) Message-ID: <49DA38C7.10006@php.net> Date: Mon, 06 Apr 2009 10:15:51 -0700 Reply-To: shire@php.net User-Agent: Postbox 1.0b10 (Macintosh/2009032714) MIME-Version: 1.0 To: Matt Wilmas CC: php-dev List , Lukas Kahwe Smith , Pierre Joye , Dmitry Stogov , Christian Seiler References: <90FF707C-391F-4FF4-8C5E-2AECEB48EB78@pooteeweet.org> <7C741E86-7720-4C87-8A43-BCC34520F0B5@pooteeweet.org> <0729A9B70D864C6E929169523CEBCB11@pc1> In-Reply-To: <0729A9B70D864C6E929169523CEBCB11@pc1> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RC2 and integer/float handling in 5.3 From: shire@php.net (shire) Matt Wilmas wrote: > Oh, other than that about the RC2 subject, I was also going to propose > some scanner changes like I mentioned to Brian on the 26th. Assuming it > works like in my head, it would basically be a big "diet" for the > scanner, making string/comment handling smaller and simpler, while > addressing the cause (for strings/comments at least) of Bug #46817 > (tokenizer misses last single-line comment) which is wrongly marked > Closed and DONE on the wiki. Before RC1, Brian reverted his changes > that, I guess, had fixed it. It is? I just tested this again to be sure something wasn't missed and it looks like it's working to me. Which test case where you using? -shire