Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:2211 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13073 invoked from network); 7 Jun 2003 18:21:37 -0000 Received: from unknown (HELO priv-edtnes57.telusplanet.net) (199.185.220.240) by pb1.pair.com with SMTP; 7 Jun 2003 18:21:37 -0000 Received: from caraveo.com ([216.232.144.94]) by priv-edtnes57.telusplanet.net (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with ESMTP id <20030607182136.DKHB21544.priv-edtnes57.telusplanet.net@caraveo.com> for ; Sat, 7 Jun 2003 12:21:36 -0600 Message-ID: <3EE22DA8.7050701@caraveo.com> Date: Sat, 07 Jun 2003 11:23:36 -0700 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: internals@lists.php.net References: <1055006122.8243.8.camel@hasele> <191168280.20030607201432@post.rwth-aachen.de> In-Reply-To: <191168280.20030607201432@post.rwth-aachen.de> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Moving to PECL From: shane@caraveo.com (Shane Caraveo) Marcus B=F6rger wrote: >=20 >=20 > Some extensions like mbstring behave different when not builtin. So > i suggest we find out which theses are and let them in. Having them in pecl in no way prevents them from being compiled builtin. > Also for extensions like ext/gd i don't see any reason to move them > out of the php main tree. Release cycles and QA, which is the only reason to do any of this at all.= Shane