Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80467
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAB6YZuzfn7LVPWtEtWfHjtomJfzye0hjM3HT+RnOzSA9TZxVkA@mail.gmail.com>
References: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me> <CAPwsocGyv7dp8n=_E1QfrXRSbYZXcHZAPk5F=hDLB070i=SCGA@mail.gmail.com>
 <4E2073DE-0951-498C-97BB-DDAC094F11FA@ajf.me> <9a033dd1f223f854e760924d118ab812@mail.gmail.com>
 <CAKUjMCU-57cDpG5ZbDGv10dSqx=Ey40D-WbKxKSnC6oSYOfLWw@mail.gmail.com>
 <2ae0164cb9b9bf1c974d7a3c60af0466@mail.gmail.com> <CAB6YZuzfn7LVPWtEtWfHjtomJfzye0hjM3HT+RnOzSA9TZxVkA@mail.gmail.com>
Date: Wed, 14 Jan 2015 17:25:34 +0200
Message-ID: <CAL0xaBEN5Vmu62xsUvhrF1pehXry3=-hQQkcwbB3d7U5cK7m0w@mail.gmail.com>
To: =?UTF-8?Q?Pavel_Kou=C5=99il?= <pajousek@gmail.com>
Cc: Zeev Suraski <zeev@zend.com>, RQuadling@gmail.com, Andrea Faulds <ajf@ajf.me>, 
	Leigh <leight@gmail.com>, PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0160bcb4064ebe050c9e5b3e
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2
From: arvids.godjuks@gmail.com (Arvids Godjuks)

--089e0160bcb4064ebe050c9e5b3e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2015-01-14 16:00 GMT+02:00 Pavel Kou=C5=99il <pajousek@gmail.com>:

> Hello,
>
> personally, as a language user, I really dislike the idea of both
> options for scalar type hinting to be the part of the language.
> Especially since you would have to declare the strict typing in each
> file (if you are going by 1 class per file in a bigger project, that's
> a LOT of declare directives to write in the long run) and if you'd
> forgot once, it would make the calling of methods somehow
> inconsistent.
>
> I wish there was just one way to do it; I don't care if the weak or
> strong variant is going to be accepted, IMHO most programmers will be
> able to adapt to either of them. The weak version makes probably more
> sense for PHP and how it handles scalar types (at least from userland
> developer's standpoint), but either of them is better than no
> typehints at all. :)
>
> PS: Personally, I find the "scalar" typehint idea useless and cannot
> find a real use case for it. Richard, would you mind giving an
> example?
>
> Regards
> Pavel Kouril


As a userland developer, have to agree with this message fully.

-1 on the v0.2 version, the declare() approach is gonna make our job
misserable after a few years when this gets adopted and misused by a lot of
people...

--089e0160bcb4064ebe050c9e5b3e--