Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82305 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 4762 invoked from network); 9 Feb 2015 18:24:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Feb 2015 18:24:42 -0000 Authentication-Results: pb1.pair.com smtp.mail=guilhermeblanco@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=guilhermeblanco@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender) X-PHP-List-Original-Sender: guilhermeblanco@gmail.com X-Host-Fingerprint: 209.85.223.170 mail-ie0-f170.google.com Received: from [209.85.223.170] ([209.85.223.170:37469] helo=mail-ie0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 72/82-25034-86BF8D45 for ; Mon, 09 Feb 2015 13:24:41 -0500 Received: by iebtr6 with SMTP id tr6so18585742ieb.4 for ; Mon, 09 Feb 2015 10:24:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=6Qw5BuQ2+/xa2JJIgQjw5bSPeRjRR5Thypkqv42TwlM=; b=xRg1lfH/efgOgKJsCoE2CNpqxZcsjtHNeE7P3GVcDGw+/aKFyE83m8yYI5YauVkS1i 08WbPilkydtRltPq47VWuJNWIZRkesSk0mQP+y/mfEtaMcFVxeT2fASsyJryUa2Si3pS jcDzkSpcTFVIsExoLZ6tS8cTHEHEZ314FaYkzzd8g+iXko3ajXD+EFUfZVv4df1A1WE8 nU0UNcIyfjuk2pELCvtqSxYCaN840x4L6kIrt5PtRffZKuBNoQCtVxA1AwgqZ5PCZt3S kHRMYWn8AHYDTI7VKxvInFhe+etwlqgNapD1Vjl88tS9pIxd3ilnF1shMCgRRY3hqWpD NR8Q== X-Received: by 10.50.107.7 with SMTP id gy7mr18534974igb.49.1423506273578; Mon, 09 Feb 2015 10:24:33 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.238.75 with HTTP; Mon, 9 Feb 2015 10:24:13 -0800 (PST) In-Reply-To: References: <8703B53E-2C4A-4AC6-95C4-D4F19C6D5221@ajf.me> <54D5659D.5000602@php.net> <54D7A6DB.3050209@seld.be> <74136F1E-817F-4A33-8228-B47045DD65C3@ajf.me> <54D7EB44.9010005@gmail.com> <54D7F972.4010107@seld.be> <2013B2A4-74E6-4452-8A48-E749DCBEA2EF@zend.com> <6C020C7F-85C0-4C88-8766-48CEDA6290F8@ajf.me> <3399a072b6cb66434e72c5f5b37d5df0@mail.gmail.com> <54D8ECCF.4000202@seld.be> Date: Mon, 9 Feb 2015 13:24:13 -0500 Message-ID: To: Andrea Faulds Cc: Andrey Andreev , Jordi Boggiano , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=e89a8ffbae41c5b973050eabe1fb Subject: Re: [PHP-DEV] [VOTE] Scalar Type Hints From: guilhermeblanco@gmail.com ("guilhermeblanco@gmail.com") --e89a8ffbae41c5b973050eabe1fb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Andrea, I totally see your viewpoint. That's why initially I voted "YES", because your proposal somehow makes sense. My when I thought over and use a weak/strict boolean type conversion on my own brain, I came to the conclusion my real wish does not get fully addressed with a "YES", leading me to switch my vote. I really wanted to expose the motivation of my change here, so everyone is aware that I do love strict typing, and I really want this in for PHP, but not in this RFC way. []s, On Mon, Feb 9, 2015 at 1:19 PM, Andrea Faulds wrote: > Hi Guilherme, > > > On 9 Feb 2015, at 18:12, guilhermeblanco@gmail.com wrote: > > > > I read again and again the RFC and I just decided to switch my vote. > > Originally a "YES" voter, I'm now a "NO" voter. I still want strict typ= es > > to exist in PHP, and not only at the end-user level, but also at the > > internals level (I can see so many optimizations around...). > > However, I think it's not an INI setting or a per file operation. I > > consider it should be (at the current PHP's pace) a heavily flexible > > support. I tend to agree that if you put "string" in its definition, yo= u > > don't want a weak type, but strict type, the same way when you put > MyClass > > instead of nothing. > > > > That's why I don't agree with the declare or "use strict" or strict. > > If I say "string $foo", I want a string, not a converted value. By > > accepting this fact, makes easier in the future to make OO primitive > types > > if we wish, and also makes everything easier for everyone... if you hav= e > > foo(string $name), you expect strict type... if you want weak type, > > foo($name). All code will work as is today, no BC breaks. > > > > That's my 2 cents... now time to update my vote in RFC. > > I can understand that viewpoint, but it=E2=80=99s not terribly kind on yo= ur users. > You=E2=80=99re basically saying that you want to force people who=E2=80= =99d prefer weak > typing to use strict typing if they use your API. It=E2=80=99s doing this= which > this RFC is designed to prevent. I don=E2=80=99t think allowing people to= force > their way on their users is a good way to deal with the lack of weak or > strict consensus in the community, no matter whether it=E2=80=99s nice fo= r API > design or not. > > Thanks. > > -- > Andrea Faulds > http://ajf.me/ > > > > > --=20 Guilherme Blanco MSN: guilhermeblanco@hotmail.com GTalk: guilhermeblanco Toronto - ON/Canada --e89a8ffbae41c5b973050eabe1fb--