Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84601 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54875 invoked from network); 11 Mar 2015 23:18:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Mar 2015 23:18:19 -0000 Authentication-Results: pb1.pair.com header.from=stelian.mocanita@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=stelian.mocanita@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.44 as permitted sender) X-PHP-List-Original-Sender: stelian.mocanita@gmail.com X-Host-Fingerprint: 209.85.215.44 mail-la0-f44.google.com Received: from [209.85.215.44] ([209.85.215.44:42773] helo=mail-la0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 52/6B-32765-93DC0055 for ; Wed, 11 Mar 2015 18:18:18 -0500 Received: by lams18 with SMTP id s18so12194493lam.9 for ; Wed, 11 Mar 2015 16:18:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=9yhR2detzK5IzsDQHs1UQFS3sKr+bYGVxCsl0mIuyf0=; b=q9f2La8a3xYUakj0FDq1+YB8gSZFZYjDVswuE1eMuGDWUcvk1vIreEzasqwi8o0Rp1 8Qmjfs8Lb+HBiga8/eALU1NzY+OL+Pl60LFCzppFB6AwZ2FX/eOnURfJz+HizIA+tfVE AM0RNMCEa3NkPGoCggs9H7Bi5prbRghkFK0LkbanrhRHnMf6hCDeFsSV4FH5POyTSYks L9bnpVJPIhtTH1mKputySRoc7kybq4AokkknfLSbipCIHwz5UQEz/yRdObKGwI17ZTFj /JzxIMcBSbgVOgNvky4K78ApvZa623KKtLtJ0Ghf9rjGqWCMHedTtR+IpTRUjBEUJP/l SdEQ== MIME-Version: 1.0 X-Received: by 10.152.203.134 with SMTP id kq6mr16928254lac.110.1426115894473; Wed, 11 Mar 2015 16:18:14 -0700 (PDT) Sender: stelian.mocanita@gmail.com Received: by 10.112.217.11 with HTTP; Wed, 11 Mar 2015 16:18:14 -0700 (PDT) In-Reply-To: References: Date: Thu, 12 Mar 2015 00:18:14 +0100 X-Google-Sender-Auth: -z5a6_euN8iKYfia1zc3YRww7cI Message-ID: To: Dmitry Stogov Cc: Nikita Popov , Bob Weinand , PHP Internals Content-Type: multipart/alternative; boundary=001a113478ec4c78d905110b7b92 Subject: Re: [PHP-DEV] [RFC] Basic Scalar Types From: stelianm@php.net (Stelian Mocanita) --001a113478ec4c78d905110b7b92 Content-Type: text/plain; charset=UTF-8 Dmitry, I tend to disagree with many people wanting this over nothing. It's a big enough topic, that raised waives in the community, to be treated properly and not just throw it in before feature freeze, so I agree with Nikita on this one. My view on it is that if both RFC's fail, the feature should not be in 7.0 and have a proper solution for 7.x, what ever that x might be, a solution that satisfies both internals and userland. On that topic, it's a shame that all this work and effort might be thrown away and at the end of the day we would be left with nothing. Regards, Stelian On Thu, Mar 12, 2015 at 12:06 AM, Dmitry Stogov wrote: > On Thu, Mar 12, 2015 at 1:53 AM, Nikita Popov > wrote: > > > On Wed, Mar 11, 2015 at 10:28 PM, Bob Weinand > wrote: > > > > > Hi all, > > > > > > after all, some people are not happy with the current proposals about > > > scalar types. So, they both still possibly may fail. > > > > > > Thus, I'd like to come up with a fallback proposal in case both > proposals > > > fail: > > > > > > https://wiki.php.net/rfc/basic_scalar_types > > > > > > It shouldn't prevent any future improvements and still give use all the > > > advantages of scalar types. > > > > > > > Before I even start thinking about this, I'd like to have clarification > as > > to whether this RFC is still eligible for targeting the PHP 7.0 release. > > The currently accepted interpretation is that all RFC votes must have > > started by March 15th, which is irreconcilable with an RFC that was only > > submitted today. > > > > Does this mean that we're delaying the PHP 7 schedule by two weeks? > > > > I feel like this topic is getting out of control. It's been discussed for > > months, now we had one vote on Andrea's withdrawn proposal, then another > > vote on Anthony's proposal, then another vote on the Zeev et al proposal > - > > and then we're going to have another one on Bob's proposal? With every > vote > > taking another couple of weeks. Hey, maybe I should also submit a STH > > proposal that we can vote on after that? > > > > If both Anthony's and Zeev's proposal fail, I would recommend to just > drop > > this topic for 7.0 and discuss it again for PHP 7.1. The necessary > > forward-compatibility changes to allow that are already proposed in > another > > RFC. > > > > Bob proposes the base common part of both other RFCs. > It actually had to be proposed in first place. > I would prefer this instead of nothing. I think many people think the same. > > Thanks. Dmitry. > > > > > > Nikita > > > --001a113478ec4c78d905110b7b92--