Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41887 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 49732 invoked from network); 13 Nov 2008 04:02:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Nov 2008 04:02:17 -0000 Authentication-Results: pb1.pair.com header.from=arnaud.lb@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=arnaud.lb@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.190 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: arnaud.lb@gmail.com X-Host-Fingerprint: 209.85.128.190 fk-out-0910.google.com Received: from [209.85.128.190] ([209.85.128.190:29253] helo=fk-out-0910.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 89/20-07308-8C6AB194 for ; Wed, 12 Nov 2008 23:02:16 -0500 Received: by fk-out-0910.google.com with SMTP id 18so765371fks.7 for ; Wed, 12 Nov 2008 20:02:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id:sender; bh=DpSltlN31nsCQOdJV740rstVuH1F1PUM4diEr5AY2AY=; b=ZXCoo3cP0OjZpJBU+7rtFsGIbTrNXoP0toMLXeWDYsmN+wrufZugPGWT53UZUV11v2 a/vRnvClRVjqjIpUwSJEQRPd4JRnqVPVZ2LYbhwdkaVGHJiSPB5yGNz0Z+CfK684vacT 3rjidCDXGTdb3m7icvZZhUkZPzXgueZ3hOwC0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:message-id:sender; b=Cd8rVwJRCQEw4uw3CG7Ro8UnftYF95hmxFC9LB/bOlu96/TTJInkKiAl0B2K5lPiTn lea5pKCCQEyizBzGj0Au0fF5uWrUvagPc5fUBTSUx3E9XdiPZPUNC56I3gegXQvIOvIw DugDYd90f1h5jgGnDS7YYOF3EXJ/fTltCTLe4= Received: by 10.180.229.17 with SMTP id b17mr3043186bkh.156.1226548933349; Wed, 12 Nov 2008 20:02:13 -0800 (PST) Received: from 207-177-41-213.getmyip.com (207-177-41-213.getmyip.com [213.41.177.207]) by mx.google.com with ESMTPS id 22sm4759623fkr.4.2008.11.12.20.02.11 (version=SSLv3 cipher=RC4-MD5); Wed, 12 Nov 2008 20:02:11 -0800 (PST) To: internals@lists.php.net Date: Thu, 13 Nov 2008 05:02:05 +0100 User-Agent: KMail/1.10.3 (Linux/2.6.26-1-amd64; KDE/4.1.3; x86_64; ; ) Cc: Lukas Kahwe Smith References: <42D56477-0E39-4548-B711-A950480E562E@pooteeweet.org> In-Reply-To: <42D56477-0E39-4548-B711-A950480E562E@pooteeweet.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-ID: <200811130502.05875.lbarnaud@php.net> Sender: Arnaud LB Subject: Re: [PHP-DEV] quick polls for 5.3 From: lbarnaud@php.net (Arnaud Le Blanc) On Wednesday 12 November 2008 20:14:31 Lukas Kahwe Smith wrote: > Hi, > 1) ext/mhash in 5.3. ext/hash has all the functions, so the entire BC > break will be that "if (extension_loaded('mhash'))" will need fixing > if mhash is removed (answer both) > I) enable ext/hash by default +1 > II) remove ext/mhash -0 > > 2) deprecate ereg*. ext/ereg is an extension as of PHP 5.3. Since ext/ > ereg is more or less redundant with ext/preg and is likely to not get > much unicode love for PHP 6, the question is if we should mark it with > a E_DEPRECATED in PHP 5.3 +1 (and allow the --without-ereg switch) > > 3) resource constants (choose one) > a) Should we deprecate constant resources (mostly used to emulate > STDIN and friends) > b) Should we instead just throw an E_STRICT > c) Document as is a > > 4) keep ext/phar enabled by default in 5.3? +1 > > 5) keep ext/sqlite3 enabled by default in 5.3? +1 > > 6) enable mysqlnd by default in 5.3? (answer both) > I) enable mysqlnd by default -0 > II) also enable ext/mysql, mysqli und pdo_mysql by default since there > will be no external dependencies in this case > > 7) should Output buffering rewrite MFH? this one comes with some > baggage, we need enough people to actually have a look at how things > are in HEAD and make it clear that they will be available for bug > fixing and BC issues resolving. the risk here is obviously that any BC > issues will be hard to isolate for end users. +0 Arnaud