Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58745
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F578D52.4080704@akbkhome.com>
References: <CAJRMtAGqZCWThbZVztGN3-FyQ4MkJAs=uO_V-6pUCy9q2aAaZw@mail.gmail.com>
 <CAKOpQSyas7HSDXD5bftK9o18ucYAfQvxRtTUjYOgRSv_4nY-9A@mail.gmail.com>
 <CAJWj5+EQhhYDTh8DHwv2N4pk8FQybX3P5H292BGixbHSLB7k3A@mail.gmail.com> <4F578D52.4080704@akbkhome.com>
Date: Wed, 7 Mar 2012 17:58:06 +0100
Message-ID: <CAMyk_AYDp1n1j-6+xhdRrb700sdqVUNmeRZf1TTt6HHP6qED2Q@mail.gmail.com>
To: Alan Knowles <alan@akbkhome.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=20cf300fb3a77ed12304baaa11d3
Subject: Re: [PHP-DEV] Scalar Type Hinting
From: linepogl@gmail.com (Lazare Inepologlou)

--20cf300fb3a77ed12304baaa11d3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

> You could try some kind of stricter casting. Where odd conversions
between array/object <-> bool/int/float/string do not work on parameter
casting .. but then you end up with two types of casting ...

I have used in depth the casting operators of C#, which are incredibly
flexible and powerful, and they are based on this exact idea. In C#, there
are two types of casting: implicit and explicit. The first is used for
trivial conversions and the later for the "odd" ones. It is possible to
classify PHP's casts into these two categories:

int to string: implicit
int to float:  implicit
int to object: explicit
int to array:  explicit
...

Once this classification is done, the code becomes much more sane. Examples=
:

function test_float( float test ) { ... }
test_float( 1.0 );  // ok
test_float( 1 );    // implicit int to float cast, ok

function test_array( array test ) { ... }
test_array( array() );  // ok
test_array( 1 );        // no implicit int to array cast, error!
test_array( (array)1 ); // explicit int to array cast, ok

I deliberately avoided using Anthony's cast-like syntax, because it does
not fit nicely here. Calling a function may cause an implicit cast, but it
will never do an explicit one.


Lazare INEPOLOGLOU
Ing=C3=A9nieur Logiciel


2012/3/7 Alan Knowles <alan@akbkhome.com>

> Comment in-line below...
>
> On Wednesday, March 07, 2012 07:10 AM, Simon Schick wrote:
>
>> Hi,:
>>
>> It got quite around that because we have some RFCs to this where the
>> functionality seems to be defined as the people thought it should be.
>> Otherwise they can raise their hands and write a mail that they want to
>> update the RFC - but as there's no one doing that, I think we're quite
>> close to what we wanted.
>>
>> Take a look at it and feel free to add your ideas in this thread.
>> https://wiki.php.net/rfc/parameter_type_casting_hints
>> https://wiki.php.net/rfc/object_cast_to_types
>>
>
> Been watching this for a while, got slightly interested in the parameter
> casting thing, but then ran a little test
> http://www.roojs.com/examples/types.php
>
> Casting on PHP may help the code inside the function, but the result is
> some weird and wonderful magic for the calling code, not to mention that
> the docs for (int) casting say the behavior may change, don't expect it t=
o
> work like that forever..
>
> You could try some kind of stricter casting. Where odd conversions betwee=
n
> array/object <-> bool/int/float/string do not work on parameter casting .=
.
> but then you end up with two types of casting ...
>
> Anyway, will go back to lurking for a while..
>
> Regards
> Alan
>
>
>> Bye
>> Simon
>>
>> 2012/3/6 Kris Craig<kris.craig@gmail.com>
>>
>>  Wow no offense, but your timing is terrible, Raymond!  We've been going
>>> back and forth on this for the past couple weeks now, though the
>>> discussion
>>> has quieted for the moment.
>>>
>>> I would suggest you go through some of the recent posts on Internals.
>>> Right now there basically is no solid consensus on this issue, though
>>> some
>>> of us have been working to change that.  But as it stands now, I'm not
>>> aware of any plans to introduce expanded typing of any kind in the
>>> foreseeable future.  And even if we did, I highly doubt it would happen
>>> before PHP 6.
>>>
>>> --Kris
>>>
>>>
>>> On Mon, Mar 5, 2012 at 6:20 PM, Raymond Irving<xwisdom@gmail.com>
>>>  wrote:
>>>
>>>  Hello,
>>>>
>>>> I came across some info on the web that states that scalar type hintin=
g
>>>>
>>> was
>>>
>>>> added to the PHP trunk but it did not make it's way into 5.4 because o=
f
>>>> objections from the community. Will it ever make it's way into 5.5?
>>>>
>>>> I know PHP is considered to be a weak typed language but it should als=
o
>>>>
>>> be
>>>
>>>> about freedom. Freedom for a PHP developer to choose to use scalar typ=
e
>>>> hinting whenever he/she sees the need.
>>>>
>>>>
>>>> Best regards,
>>>> __
>>>> Raymond
>>>>
>>>>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--20cf300fb3a77ed12304baaa11d3--