Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82181
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <8703B53E-2C4A-4AC6-95C4-D4F19C6D5221@ajf.me>
References: <8703B53E-2C4A-4AC6-95C4-D4F19C6D5221@ajf.me>
Date: Sun, 8 Feb 2015 23:18:41 +0100
Message-ID: <CAH-PCH5MbjvC5aqBNZ9b=tmvXCvNUv9drCv1B3vFiErSP2A6=w@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c1b4243d558b050e9b09e2
Subject: Re: [PHP-DEV] [VOTE] Scalar Type Hints
From: tyra3l@gmail.com (Ferenc Kovacs)

--001a11c1b4243d558b050e9b09e2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 5, 2015 at 9:14 PM, Andrea Faulds <ajf@ajf.me> wrote:

> Good evening,
>
> At long last, I=E2=80=99m going to put the RFC to a vote. It=E2=80=99s be=
en long enough -
> I don=E2=80=99t think there needs to be, or will be, much further discuss=
ion.
>
> I=E2=80=99d like to make sure that everyone voting understands the RFC fu=
lly.
> Please read the RFC in full: the details are important. And if  anyone ha=
s
> any questions or uncertainties, please ask them before voting. I am very
> happy to answer them.
>
> I would urge everyone who wants type hints to vote for this RFC. It is no=
t
> a perfect solution, but there can be no perfect solution to this issue.
> However, I think it is better than most of the alternatives suggested thu=
s
> far - see the rationale section, and previous discussions. Crucially, thi=
s
> RFC would keep PHP a weakly-typed language, and not force either strict
> typing, nor weak typing, on anyone who does not want it. It would allow t=
he
> addition of type hints to existing codebases. It would not create a
> situation where userland functions are strict yet internal functions are
> not, because the strict mode affects both. I=E2=80=99ve tested the implem=
entation
> myself on my own code, and it worked well, providing benefits other
> proposals would not have given (see my previous post about my experiences=
).
>
> Voting starts today (2015-02-05) and ends in two weeks=E2=80=99 time (201=
5-02-19).
> In addition to the vote on the main RFC, there is also a vote on the type
> aliases issue, and a vote to reserve the type names for future RFCs=E2=80=
=99 sake
> if this RFC fails.
>
> The RFC can be found here, and it contains a voting widget:
> https://wiki.php.net/rfc/scalar_type_hints
>
> Thank you for your time.
>
> --
> Andrea Faulds
> http://ajf.me/
>
>
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
hi,

I've voted no for two reasons:
1, I don't really like the the proposed declare solution, I know that you
put much thought and effort with finding a way to make the strict hints
opt-in for the caller, but I think it is still not a good compromise:
people in favor of strict hints will hate it because it is opt-in from the
caller, so they can't use scalar hints to save the boilerplate for argument
validation, and other people like me will unlike it because they think that
the blockless declare will cause many errors and debugging headache when
somebody moves some code between files (or concatenating files as part of
their deployment process).
2, As this is a really polarizing topic I would like if the eventual
solution would have wider support from the current php-src regular
contributors, and not just pushed through by "force". (And I know that
status quo sucks when somebody trying to do innovative stuff, but it is a
safe thing to default to).

Thanks for your efforts on such a hard topic and I hope you can eventually
succeed where everyone else failed thus far!

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--001a11c1b4243d558b050e9b09e2--