Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:9635
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Sun, 2 May 2004 19:17:32 +0200
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <6310142916.20040502191732@marcus-boerger.de>
To: Andi Gutmans <andi@zend.com>
Cc: internals@lists.php.net
In-Reply-To: <5.1.0.14.2.20040502190058.01fa47a0@127.0.0.1>
References: <243202120.20040501220932@marcus-boerger.de>
 <5.1.0.14.2.20040502190058.01fa47a0@127.0.0.1>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Type hints
From: helly@php.net (Marcus Boerger)

Hello Andi,

Sunday, May 2, 2004, 6:09:22 PM, you wrote:

> Hi Marcus,

> I wouldn't use the syntax you proposed but you:
> function func(MyClass $obj or null);

an updated patch can be found here:
http://somabo.de/php/ext/ze2/ze2-type-hints-20040502.diff.txt


> Concerning type hints, I don't think that a type hint of "class" is useful.
> If you don't use a base class as a type hint (which you will almost always
> use) then how useful will this really be? Also, it's not really Class but 
> it's an Object, so we'd have to add another reserved word. In my opinion, 
> I'd only go with the "array" part of the typehints patch.
the updated patch neither contain 'class' not 'object'. Adding Object as a
reserved work is a bad ide imo because i thing many ppl use it for basic
classes. The reasons i chose class in the first place were that i didn't
want to add a new keyword and that i had the term 'instance of any class'
in mind.

> On another note, I think PHP 5 is already stable and quite mature. It's an
> order of magnitude more stable than PHP 4 was when it was released. I think
> we should start thinking of a deep feature freeze and a release date. As 
> we're in the beginning of May I think sometime towards July makes sense. 
> This does mean that we really need to stop adding stuff. I agree to open 
> the typehints issue because it could potentially lead to a BC break 
> depending what solution we take.
more or less agreed. what i fear is missing the chance to act on bad test
experience. but we can't wait forever, so how about a branch now, that
could attract even more testers and hence give more feedback?

best regards
marcus