Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44220 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 49413 invoked from network); 10 Jun 2009 16:21:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Jun 2009 16:21:34 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 83.243.58.134 as permitted sender) X-PHP-List-Original-Sender: johannes@php.net X-Host-Fingerprint: 83.243.58.134 mailout2.netbeat.de Linux 2.6 Received: from [83.243.58.134] ([83.243.58.134:33982] helo=mailout2.netbeat.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 14/25-50806-D8DDF2A4 for ; Wed, 10 Jun 2009 12:21:34 -0400 Received: (qmail 11526 invoked by uid 89); 10 Jun 2009 16:53:34 -0000 Received: from unknown (HELO ?192.168.1.102?) (johannes%schlueters.de@93.104.117.198) by mailout2.netbeat.de with ESMTPA; 10 Jun 2009 16:53:34 -0000 To: Guilherme Blanco Cc: PHP Internals In-Reply-To: References: <1244645012.6252.110.camel@goldfinger> Content-Type: text/plain Date: Wed, 10 Jun 2009 18:21:29 +0200 Message-ID: <1244650889.6252.115.camel@goldfinger> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Last steps towards 5.3.0 From: johannes@php.net (Johannes =?ISO-8859-1?Q?Schl=FCter?=) Hi, On Wed, 2009-06-10 at 12:14 -0300, Guilherme Blanco wrote: > 1- Will it include new autoloader definition that standards group was > talking about? No proposal, no code, ... > 2- I still have a BC break that I cannot isolate (huge codebase). I'm > trying to find it and once I isolate it and report, will the fix be > included before 5.3.0 final? Maybe. Everything else depends on the case and can't be said in a generic way. The overall goal is not to have too many BC issues - besides lot's of deprecation warnings the only real problem I ever found in multiple applications was related to call_user_func_array() in combination with bad usage of references, but that one hit a few projects I saw. johannes