Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77177
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain hotmail.com designates 157.55.2.106 as permitted sender)
Message-ID: <DUB121-W41229E79856FEDA59BEC06ECCB0@phx.gbl>
Content-Type: multipart/alternative;
	boundary="_28d97512-f5a5-4d83-8ab8-ddf561880179_"
To: Andrea Faulds <ajf@ajf.me>, "internals@lists.php.net"
	<internals@lists.php.net>
Date: Sun, 14 Sep 2014 11:26:12 +0100
Importance: Normal
In-Reply-To: <6893A97A-EC4C-4124-B804-96E2A26B953F@ajf.me>
References: <6893A97A-EC4C-4124-B804-96E2A26B953F@ajf.me>
MIME-Version: 1.0
Subject: RE: [PHP-DEV] [VOTE][RFC] Scalar Type Hinting with Cast
From: unassailable007@hotmail.com ("Thomas .")

--_28d97512-f5a5-4d83-8ab8-ddf561880179_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable



> From: ajf@ajf.me
> Date: Sun=2C 14 Sep 2014 00:30:40 +0100
> To: internals@lists.php.net
> Subject: [PHP-DEV] [VOTE][RFC] Scalar Type Hinting with Cast
>=20
> Good evening=2C
>=20
> I=92ve given up on my plan B=2C so I=92m putting this RFC=2C finally=2C t=
o a vote.
>=20
> I would urge you to vote in favour. It is not going to please everyone=2C=
 it is after all a compromise proposal. However=2C I have tried my best to =
strike a balance between complete weak typing and strict typing. If this pa=
sses=2C we will finally have userland type specifiers for scalar types. It=
=92s not perfect=2C but I=92d argue it=92s far better than nothing.
>=20
> Voting starts today=2C 2014-09-14=2C and ends in a week=92s time=2C 2014-=
09-21.
>=20
> Thanks!
>=20
> https://wiki.php.net/rfc/scalar_type_hinting_with_cast#vote
> --
> Andrea Faulds
> http://ajf.me/
>=20
>=20

RE: [PHP-DEV] [VOTE][RFC] Scalar Type Hinting with CastThomas Punt  11:23 T=
o: Andrea Faulds> From: ajf@ajf.me
> Date: Sun=2C 14 Sep 2014 00:30:40 +0100
> To: internals@lists.php.net
> Subject: [PHP-DEV] [VOTE][RFC] Scalar Type Hinting with Cast
>=20
> Good evening=2C
>=20
> I=92ve given up on my plan B=2C so I=92m putting this RFC=2C finally=2C t=
o a vote.
>=20
> I would urge you to vote in favour. It is not going to please everyone=2C=
 it is after all a compromise proposal. However=2C I have tried my best to =
strike a balance between complete weak typing and strict typing. If this pa=
sses=2C we will finally have userland type specifiers for scalar types. It=
=92s not perfect=2C but I=92d argue it=92s far better than nothing.
>=20
> Voting starts today=2C 2014-09-14=2C and ends in a week=92s time=2C 2014-=
09-21.
>=20
> Thanks!
>=20
> https://wiki.php.net/rfc/scalar_type_hinting_with_cast#vote
> --
> Andrea Faulds
> http://ajf.me/
>=20
>=20

From a user-land developer perspective=2C I really detest this feature bein=
g added into PHP. If PHP has features that will make it a stronger-typed la=
nguage=2C then it will undoubtedly lose its loosely-typed and forgiving nat=
ure eventually. The evangelists for making PHP a strongly-typed language wi=
ll boast of its benefits (which will have some truth=2C in all fairness)=2C=
 and this will only lead to the condemnation of PHP code that doesn't use t=
hese stricter language features (slowly converting PHP into a stricter lang=
uage). This isn't the easy-going and generally-liked nature of the PHP lang=
uage in _any_ way. Whilst I can see there are benefits of making PHP strict=
er=2C I for one would rather keep PHP as a loosely-typed and forgiving lang=
uage. After all=2C if I wanted to use a strongly-typed language for buildin=
g websites=2C then I'd be using Java instead.
The only part of the discussion I liked on this topic was the ability to us=
e explicit type casts as part of the function signature. Whilst it is a bit=
 of a syntactic sugar (which will cut out on some PHP code in the function =
body too)=2C it does give the function parameters some sort of signature th=
at will show their expected set of values (assuming developers know the cas=
ting rules=2C of course).
-Tom
(P.s sorry for the double email Andrea=2C I accidentally sent this to you o=
nly the first time...)>=20
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe=2C visit: http://www.php.net/unsub.php
>=20
 		 	   		  =

--_28d97512-f5a5-4d83-8ab8-ddf561880179_--