Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26409
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain l-i-e.com from 67.139.134.202 cause and error)
Message-ID: <59809.208.195.234.246.1162925137.squirrel@www.l-i-e.com>
In-Reply-To: <2F.C5.05668.5BD50554@pb1.pair.com>
References: <7f3ed2c30611031000j2dc48a6amb7f04c8011442b56@mail.gmail.com>
    <282B7D4B-DC15-4ABC-95A6-C03F766C19B7@prohost.org>
    <27664.208.195.234.246.1162844322.squirrel@www.l-i-e.com>
    <10845a340611070126hdd3cfe1v4f62a37d98f620e1@mail.gmail.com>
    <2F.C5.05668.5BD50554@pb1.pair.com>
Date: Tue, 7 Nov 2006 12:45:37 -0600 (CST)
To: "Ron Korving" <r.korving@xit.nl>
Cc: internals@lists.php.net
Reply-To: ceo@l-i-e.com
User-Agent: Hostbaby Webmail
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal
Subject: Re: [PHP-DEV] [PATCH] Scalar type hinting ;)
From: ceo@l-i-e.com ("Richard Lynch")

On Tue, November 7, 2006 4:19 am, Ron Korving wrote:
> I wouldn't like E_NOTICE. I agree that the result should be a NULL
> value if
> a conversion fails,

Assume, for the sake of argument, that someday one's type-hint could be:

function foo ([NULL | int] $bar){
}

Also assume the paramter passed to $bar is '42'

Then is converting to NULL really the right answer?...

I don't have a BETTER answer, mind you...

Seems to me, though, that if you're willing to turn on type-hinting,
and you restrict your function to accept only [NULL | int], then I'd
be more happy with PHP throwing something bigger than E_NOTICE and
converting the input to NULL and carrying on...

Seems to me, that once you commit to the type-hinting, a failed
conversion oughta be E_ERROR...

> I don't see a point in a hint called "mixed" either. You might as well
> not
> use a hint for that particular function parameter.

You may need [mixed] if the PHP Manual under-documents what return
values occur in the case of errors (which is the current
state-of-the-art, really) and you don't know for sure what is going to
come back, but you want something there, just so you know it's "not
right yet"

>> Sometime after that the facility to make the hints become enforcers.
>> There would be a published list of conversion mechanisms (the
>> equivalent PHP function in effect). You could potentially allow user
>> defined conversions for user defined types though I would see this
>> as
>> a WIBNI, rather than a MH.

WIBNI?
MH?
[shrug]

I get the gist from context, but may be missing details... :-)

-- 
Some people have a "gift" link here.
Know what I want?
I want you to buy a CD from some starving artist.
http://cdbaby.com/browse/from/lynch
Yeah, I get a buck. So?