Antony Dovgal wrote: > On 01.08.2008 14:11, Antony Dovgal wrote: >> I can agree that disabling something that was already enabled in 5.2 >> might create some confusion, but why enable scarcely created >> extensions by default, especially if they are known to cause lost of >> obscure problems in the past (like Phar)? > > See http://bugs.php.net/bug.php?id=45613 for example. > Who would have thought that there are multithreaded web-servers, eh? > > I'm going to disable ext/phar before alpha2. > You've been warned.
Hi, I've just returned home finally, and look forward to taking a look at issues. I even committed 2 new code coverage tests while on the road, in case you doubt my resolve to fix things up. Tony, please drop the posturing, it makes you look somewhat ridiculous :). I *explicitly* asked that the question of enabling phar by default be voted on prior to rc 1 when I enabled it, and again reminded about it a month later. Please see the links below to the emails in question. Let's not forget - disabling ext/phar by default involves changing a 1 to a 0 in config.m4, it's hardly difficult to do. I agree that it needs to happen prior to the final release cycle or not at all. Is alpha2 the new rc1? That makes no sense to me if so. Thanks, Greg >From May 14, 2008: http://marc.info/?l=php-internals&m=121078127525090&w=2 >From June 23, 2008: http://marc.info/?l=php-internals&m=121419199122615&w=2 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
