Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49295
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=LSc2fh3c9rKiC4Ruf7auXRjlEsCBD9Fkotdh4rd/Xrvy5QkWBGW5olU5r6gau1L4NT
         A5gSNmLdxJY3mhGjFqdnn7eqpNoV2XU1lHYjWCuEahK8Rj4jdlIVeNsxQvXo2JKCXDPN
         Bo75xVIvQNZLqDkdwNrb51tnQZnEjLiH7MYw8=
MIME-Version: 1.0
In-Reply-To: <4C61D6D0.90907@sugarcrm.com>
References: <AANLkTim7sNwZWyo8dQz-o6S=Tta-OGYqnDM0cDJX3A49@mail.gmail.com>
	<1281478269.6608.292.camel@guybrush>
	<alpine.DEB.2.00.1008102325440.29410@kossu.derickrethans.nl>
	<4C61D6D0.90907@sugarcrm.com>
Date: Wed, 11 Aug 2010 03:08:37 +0400
Message-ID: <AANLkTinATNjUXa1WUNBpFu0tL8LTd091H1jRPP9iiRSv@mail.gmail.com>
To: Internals <internals@lists.php.net>
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Strict typing (was: Typehints)
From: crocodile2u@gmail.com (Victor Bolshov)

Having two similar syntaxes that work differently - would make the
situation even worse that it is now - I beleive. And I totally agree
with Rasmus - strict typed language mustnt be called PHP. (Just a poor
user's notice to all of you internals' geeks out there)

2010/8/11 Stas Malyshev <smalyshev@sugarcrm.com>:
> Hi!
>
>> 1. right now we *have* strict type checks for classes and arrays in the
>> =9A =9Aform of "classname" or "array"
>
> Because classes and arrays were never intechangeable types and there was
> never implicit or explicit conversion between SplRecursiveTreeIterator an=
d
> Zend_Pdf_Generator - it doesn't even make sense to suggest it. There alwa=
ys
> was conversion between int and string or int and bool. These two things a=
re
> completely different.
>
>> 2. the strict scalary type hint patch reuses this same syntax in the
>> =9A =9Aform of<type-name> =9Ato do the same thing in function arguments
>
> It's not a good thing. As I mentioned, primitive types and classes are ve=
ry
> different in their use cases and established patterns in PHP. Primitive
> types are largely interchangeable, classes are not. (As for arrays, array=
s
> really should be a class by their usage patterns etc. but for historic
> reasons... you know)
>
>> 3. we have casting type hints in the rest of the code in the form of
>> =9A =9A"(int)".
>
> Just to make it simpler and less confusing, of course. It's nothing like
> language having two features that look almost exactly the same but work i=
n
> different way, and using plenty of ()s is an added bonus for all Lisp fan=
s
> out there.
>
>> Some people don't like strict typehints, but the syntax as it currently
>> is regarding type hints is *consistent*. Now, to allow both strict and
>> casting hints, the logical step seems to be, to give the weak typehint
>> advocates their tool as well:
>
> Calling something that works completely differently from all the establis=
hed
> patterns of PHP - like internal functions, etc. - "*consistent*" requires
> totally new definition of this word.
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



--=20
=F3 =D5=D7=C1=D6=C5=CE=C9=C5=CD,
=F7=C9=CB=D4=CF=D2