Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82913 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 86433 invoked from network); 17 Feb 2015 01:20:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Feb 2015 01:20:57 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.46 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.192.46 mail-qg0-f46.google.com Received: from [209.85.192.46] ([209.85.192.46:55629] helo=mail-qg0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 27/12-08417-87792E45 for ; Mon, 16 Feb 2015 20:20:56 -0500 Received: by mail-qg0-f46.google.com with SMTP id z107so25872073qgd.5 for ; Mon, 16 Feb 2015 17:20:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7qpwEEZcTmeV5jlsZU6N0wtulYWwvvsf3h40OE6CfiU=; b=zWGD1ZgSZHW+fhXcERJ/npwxjm8EXm2gJhGPbGwUUkgzWAQRKSm4jRmHcmYkrWnAnz iAktUEZEpnNHLxQcFgsC1HTKp672MuefoG3TZJF8sMAvF57WtMB+SG6PDXHRmKpdwZmN NjbfobE4oNXN1Y3gdJp4KJiQ52AFIACs0YSSTbRBNXFyEBTtYlIioEHPzJMrdye3J7z5 ABGa6iRQozl3QvwWbmfOF3NbFtRiNnEQVGkZ2fONIKjn+aRe2Ui0xy8ZN4EbB+JeifiK ajvw2HrZm3wqu7NhcrIyrwcXXAiXviKV5SY89iXUtqi1M7y+QRuQsA3dEmihRLsIlkHf eOZQ== MIME-Version: 1.0 X-Received: by 10.229.19.68 with SMTP id z4mr1066373qca.14.1424136053263; Mon, 16 Feb 2015 17:20:53 -0800 (PST) Received: by 10.96.39.195 with HTTP; Mon, 16 Feb 2015 17:20:51 -0800 (PST) Received: by 10.96.39.195 with HTTP; Mon, 16 Feb 2015 17:20:51 -0800 (PST) In-Reply-To: References: <011801d04a07$83ab1c00$8b015400$@php.net> Date: Mon, 16 Feb 2015 17:20:51 -0800 Message-ID: To: Dmitry Stogov Cc: Rowan Collins , PHP internals , Arvids Godjuks , Jefferson Gonzalez , francois@php.net Content-Type: multipart/alternative; boundary=001a11343a4c9123c4050f3e83c3 Subject: Re: [PHP-DEV] Reviving scalar type hints From: pierre.php@gmail.com (Pierre Joye) --001a11343a4c9123c4050f3e83c3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Feb 16, 2015 10:56 AM, "Dmitry Stogov" wrote: > > On Mon, Feb 16, 2015 at 7:42 PM, Fran=C3=A7ois Laupretre > wrote: > > > Hi, > > > > > > De : Arvids Godjuks [mailto:arvids.godjuks@gmail.com] > > > > > > The 0.1 RFC version was mentioned a lot as a good compromise by many > > > people > > > and had major support. > > > Maybe someone competent could pick it up, make necessary adjustments > > > that > > > where required and let people vote on it? Start with small steps - ge= t > > the > > > weak type hints into the language first, see how it gets used and then we > > > can always add strict type hints if there is a need/desire to do that= . > > > > > > That way we finally get type hints into the language, and those wanting > > the > > > strict variety have all the opportunities in the world to add them at a > > > later release with proper discussion and development time. > > > > That's what I am planning. If I write an RFC, it will be based on Andrea's > > 0.1/0.2 version, and won't propose different modes. > > > > I would propose exactly Andrea's 0.1. > Most people were agree to support weak type hints by default. So a 50/50 vote is most people in favor of one type? Sorry, this is not the case. > This proposal won't prevent feature addition of optional strict type hints. > All are tired from endless arguing. Yes, we are. The only difference is one camp makes compromises and tried to find solutions. Now, deja vu scenario, we are heading exactly to what you want because we do not have any other solution. A by default single choice is not good. This is a very bad move. --001a11343a4c9123c4050f3e83c3--