Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42789 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66061 invoked from network); 22 Jan 2009 19:48:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Jan 2009 19:48:21 -0000 Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 88.198.8.16 bigtime.backendmedia.com Linux 2.6 Received: from [88.198.8.16] ([88.198.8.16:47765] helo=bigtime.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4F/6D-15341-48DC8794 for ; Thu, 22 Jan 2009 14:48:21 -0500 Received: from localhost (unknown [127.0.0.1]) by bigtime.backendmedia.com (Postfix) with ESMTP id B23591EBC013; Thu, 22 Jan 2009 19:48:55 +0000 (UTC) X-Virus-Scanned: amavisd-new at backendmedia.com Received: from bigtime.backendmedia.com ([127.0.0.1]) by localhost (bigtime.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q7a03D2UsO0K; Thu, 22 Jan 2009 20:48:53 +0100 (CET) Received: from [192.168.0.151] (77-58-151-147.dclient.hispeed.ch [77.58.151.147]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mls@pooteeweet.org) by bigtime.backendmedia.com (Postfix) with ESMTP id B0A12414400B; Thu, 22 Jan 2009 20:48:51 +0100 (CET) Cc: Christian Seiler , =?ISO-8859-1?Q?David_Z=FClke?= , Stanislav Malyshev , Marcus Boerger , Ionut Gabriel Stan , internals@lists.php.net, Dmitry Stogov , =?ISO-8859-1?Q?Johannes_Schl=FCter?= Message-ID: To: Pierre Joye In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Thu, 22 Jan 2009 20:48:12 +0100 References: <1016989528.20090112233204@marcus-boerger.de> <49743A89.3070607@zend.com> <995073772.20090119125721@marcus-boerger.de> <4974B2C8.5000704@zend.com> <49760CDF.2080006@gmx.net> <062274D5-9C20-4129-9597-145354A704EE@bitextender.com> <76BB6A71-62B3-4F0F-BB30-89CA7BAF5BD3@pooteeweet.org> <497880E8.5080202@gmx.net> <4978BCB7.7000000@gmx.net> X-Mailer: Apple Mail (2.930.3) Subject: Re: [PHP-DEV] [RFC] Object extension, $this binding of closures, chat results From: mls@pooteeweet.org (Lukas Kahwe Smith) On 22.01.2009, at 20:39, Pierre Joye wrote: > hi, > > On Thu, Jan 22, 2009 at 7:36 PM, Christian Seiler > wrote: >> Hi again, >> >> ok, I just verified that the current PHP 5.3 CVS has the same >> behaviour >> as PHP 5.3 alpha 3 (which is the original design). So basically, I'd >> suggest the following: >> >> * Feature freeze as Lukas and Johannes had planned tomorrow with *no* >> more changes wrt. closures for beta1, then release beta1. >> >> * For post-beta1: Discuss which of the following options we want to >> take: >> >> a) My Closure::bind() compromise >> b) Leave as is in order to add Closure::bind() later (5.3.1, 5.4, >> 6.0) when we've discussed all the details. >> c) Drop $this/OOP support from closures for beta2 in order to be >> able to discuss this properly for a later version. > > If we know limitations, issues or design problems now and they can be > fixed in a relatively short delay (within a couple of weeks), then I > do not see why we should release 5.3.0 with them. We are in a test > phase and that means that we will have to change one thing or another, > even after beta1. That's what I meant in my previous posts. right .. we are in a test phase .. not experiment phase. the time for experiments is over. we have enough features for a couple releases. so if we find that some feature is not done yet .. or that we might need to break BC later if we release the feature now, then we should strip the feature until we do not foresee possible BC breaks and move on. if we keep delaying a few weeks here and there, we will do PHP a greater disservice. as johannes has pointed out we have delayed some features because we wanted to focus on getting 5.3 out. if necessary we can always have a PHP 5.4 just as well. regards, Lukas Kahwe Smith mls@pooteeweet.org