Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55052 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 298 invoked from network); 1 Sep 2011 09:22:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Sep 2011 09:22:46 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.42 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 74.125.83.42 mail-gw0-f42.google.com Received: from [74.125.83.42] ([74.125.83.42:62360] helo=mail-gw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 06/69-44095-4EE4F5E4 for ; Thu, 01 Sep 2011 05:22:45 -0400 Received: by gwb17 with SMTP id 17so797378gwb.29 for ; Thu, 01 Sep 2011 02:22:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=zqlBu3qOyv1a/8pORAk0mVXTBWdy3i99lVo716L9O1Y=; b=VQce5eE1pQUgglDtlPTudbXPAyZKF+6m4udcVEM0/CvOwPceMjW2znOTeB8NOwS2is i1Anj4w4UAOEb3yIiQ4vMjcF8FXzZKrTOcuqhyX3IvHTLIV04TWYIEtZAgfvVbkMMCYf sgzdQUjecg+VVlxxGM664Pbx880FMOi1RkSnQ= MIME-Version: 1.0 Received: by 10.150.160.9 with SMTP id i9mr12170ybe.29.1314868960518; Thu, 01 Sep 2011 02:22:40 -0700 (PDT) Received: by 10.147.182.15 with HTTP; Thu, 1 Sep 2011 02:22:40 -0700 (PDT) Date: Thu, 1 Sep 2011 11:22:40 +0200 Message-ID: To: PHP internals Content-Type: text/plain; charset=ISO-8859-1 Subject: drop bison 1.x? From: pierre.php@gmail.com (Pierre Joye) Hi, It would help a lot to test the parser if we drop bison 1.x support. It won't change anything in the parser rules or in the code base but only the way we test it. Bison version 1.x has different messages than 2.x (formats and contents). It causes some tests to fail because of these different messages. I wonder if we could simply stop to support bison 1.x in 5.3 and later or at least in 5.4+. But if we do it in 5.4+ only it will be harder to maintain both tests synced and compared the results between the two branches (eventual BC breaks or similar breakages). Comments? Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org