Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39527
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain daylessday.org designates 89.208.40.236 as permitted sender)
Message-ID: <4892E5DD.50907@daylessday.org>
Date: Fri, 01 Aug 2008 14:30:53 +0400
User-Agent: Thunderbird 2.0.0.14 (X11/20080421)
MIME-Version: 1.0
To: Scott MacVicar <scott@macvicar.net>
CC: php-dev <internals@lists.php.net>
References: <4892E15D.1080004@daylessday.org> <4892E37B.8060804@macvicar.net>
In-Reply-To: <4892E37B.8060804@macvicar.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] enabling everything by default
From: tony@daylessday.org (Antony Dovgal)

On 01.08.2008 14:20, Scott MacVicar wrote:
> ext/pdo_sqlite and ext/sqlite3 use the same underlying lib so its just 
> another wrapper but without the PDO crap on top.

I know, I know.
But why enable it by default (as well as PDO_SQLITE)? 
What's so extremely useful in this extension that every user needs it?

> If you have ideas on testing without enabling them or bundling in the 
> build please do share. It's a chicken and egg situtation imho.

Testing doesn't require enabling it by default.
In fact, it doesn't even require putting the extension in the core, 
though this surely increases the the amount of feedback.
Developers should test their extensions, not users.

-- 
Wbr, 
Antony Dovgal