Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:87846 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96688 invoked from network); 21 Aug 2015 21:30:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Aug 2015 21:30:13 -0000 Authentication-Results: pb1.pair.com header.from=cmbecker69@gmx.de; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=cmbecker69@gmx.de; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.21 as permitted sender) X-PHP-List-Original-Sender: cmbecker69@gmx.de X-Host-Fingerprint: 212.227.17.21 mout.gmx.net Received: from [212.227.17.21] ([212.227.17.21:55566] helo=mout.gmx.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 22/71-19109-B5897D55 for ; Fri, 21 Aug 2015 17:30:05 -0400 Received: from [192.168.0.100] ([88.134.66.33]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0LhSfM-1YxyzX3Lxg-00mXOY; Fri, 21 Aug 2015 23:29:52 +0200 To: Anatol Belski , 'Nikita Popov' References: <55CA26DF.3030109@gmx.de> <03dd01d0d476$c75b6730$56123590$@belski.net> <55CA646F.8020506@gmx.de> <040101d0d4ca$656f4e20$304dea60$@belski.net> <55CC80FC.5070306@gmx.de> <066a01d0d61f$4937d370$dba77a50$@belski.net> <036401d0dc51$23f45060$6bdcf120$@belski.net> Cc: 'Adam Harvey' , 'Christoph Becker' , 'PHP internals' Message-ID: <55D79858.8080506@gmx.de> Date: Fri, 21 Aug 2015 23:30:00 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <036401d0dc51$23f45060$6bdcf120$@belski.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:bbfCA0RdlfG+mpqx5l7AOW2JQmHJcxynAJRI5LD1tzl16ZYfUZN WkObwi3q+kNxtZtRRecNLRp8Z1LWkUhSMy7wdbaEQmcJghYt+vwojHMtv4J8gEl9L8jbZWk dhSTEWA2PCbcSKTR9BHVZc1Vamg+3tJNx5kB/aevb5OXgmxrUklCFdKOcyZYuV7azDDAeVq gSzXGb/WE33XFkIuwi5DA== X-UI-Out-Filterresults: notjunk:1;V01:K0:1a2FLXpkuAs=:JTkb9gy0qNkP/gng11Yzj8 Q6D5OAv9fE5GO0g65207VZMzaWv3MUlEziVTUB8f7Jr9V7JMJuyOhvxLeSNAXsbv9k+Fj3l2+ 86wMd61mq5TWdxfaEK2M2DceiXx/L7wJTXegWPPuRfVos6uiqfpHfwKB3M4cJT4iWSqXhyNVE MQO+qddUzPa7dn9FhKwksD8WXzumbB6qPAbZEQSmDu9+BKuyBMbUsjTS1dVEc8rfZmlq8XTdO KGvAZhLnYA/Sqcy8YTNbpdskE3Xw1KmImrF1k2bwEGOmYn3WWa0wgv7d+4+j8bVsx6Tl181lY neLsmQW10QyOckJV1HB28cSqCF7xF9qTR9NLrcfIZDITj+clKcdIaSL34SfRSrJngwFmABVWY L993NgMAVESI/F6vSt+X1o4A8aqly9fFKWWipNbm58/l0cQ1en+5hzUFDgMx2ZK7hbFhKoGmm 1VwnzoRmtw5YORGV9kfG0qOmMd6WshQVsrdOdpZ3vm7cowIZE27tFlRlTmFiKyg/QQi3wAX+R cLGoybd0Qk1DHuE6wCXNGF+msikBo5zrQ+GEBkVKD0e3iNp8XNd7tAaf0lpgVdbnINODv+LRa eP17CSPgEQvW2dMd0RW5xlKDcTdO+H0OMYwOEo7+nABVDFtfmYPfX53dsQ7w/Y+VZ46CqY7Jh pc/QLPkizyCT2RlxF35de2WOuYTZmEubq+hdGvuz+4qdM4bnEAGW7cwqFHSUnazyG3xglwxOw CuLy/ssruV5fjl4THf9St7cEInt6ke8LLnzxbw== Subject: Re: [PHP-DEV] libpcre version requirements From: cmbecker69@gmx.de (Christoph Becker) On 21.08.2015 at 22:37, Anatol Belski wrote: >> -----Original Message----- >> From: Nikita Popov [mailto:nikita.ppv@gmail.com] >> Sent: Friday, August 21, 2015 3:14 PM >> To: Anatol Belski >> Cc: Adam Harvey ; Christoph Becker >> ; PHP internals >> Subject: Re: [PHP-DEV] libpcre version requirements >> >> There already was some discussion about bumping the libpcre version for 5.6. I'll >> quote what I said back then: >> >>> [...] I think the low version requirement is bad for other reasons: >> There's a big gulf in terms of both features and bug fixes between PCRE 6.6 and >> what PHP currently bundles. It's a bit ridiculous that you can end up using a PHP >> version from 2014 together with a decade old PCRE version. >> >> and >> >>> It would still be nice to increase the minimum version number [...], >> because allowing prehistoric PCRE versions in a new release makes zero sense. I >> recommend at least 8.10 because it both supports marks and - more relevantly >> to most users - supports UCP mode, which PHP uses by default (if available). UCP >> mode can significantly change the behavior of PCRE with the /u modifier, as >> such guaranteeing a minimum version of 8.10 will also guarantee a somewhat >> consistent /u behavior. >> >> Basically, if we allow a too broad range of PCRE versions, we also allow a broad >> range of behavior people have to deal with. If people use the /u modifier, they >> will get significantly (and at the same time subtly) different behavior if PHP was >> linked against libpcre newer or older than 8.10. >> >> Distros that will ship with PHP 7 will also ship with new PCRE versions. >> External package repositories with PHP 7 will also have newer PCRE versions. >> People compiling themselves use the bundled version. >> >> Let's bump this. If you install PHP 7 in 2016 you should *not* have to deal with a >> PCRE version released in 2006. > > Yeah, I read this discussion here http://grokbase.com/t/php/php-internals/142wrqvs7p/add-support-for-pcre-marks . Seems it was not finished for some reasons. > > I was mentioning "if it doesn't block the future development" exactly for the reason to hear if there's something. Now turns out there are at least two issues (count yours and Christoph's one) requiring a newer PCRE. Nevertheless - I'd prefer to keep the current situation for 7.0 and do it directly in master after 7.0 was branched which is merely a month away. Primarily to keep 7.0 compatible in as much areas as possible. Also worried a bit about that other 60% from the stats which are not Linux, Linuxes look actually good having >8.10 even for old stable. But that also means - keeping or not an option to use a lower version doesn't really hurt (at least for the popular distros like Debian, Ubuntu, Fedora). > > Also about the future work - IMHO it would make sense to start a port for PCRE2 at some point in autumn (and I'm intended to if no one started earlier) to target 7.1 or later. Regarding PCRE - it most likely won't get any new features but bug fixes only, PCRE2 is what were future oriented. 7.0 won't arrive in the distros earlier than in a yeah, or alike. And by that time that can be completely another priority. > > So concluding - preferably were to keep the PCRE version for 7.0 and raise in master, unless you see some hard issue or want to make use of "new" features in PCRE 8.x that can't wait anymore, then please do now. Would it be an acceptable compromise for everybody to stick with the current *requirements* for now, but to document[1] that PCRE >= 8.10 is *recommended* for PHP 5.6 and 7.0? [1] -- Christoph M. Becker