Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:10465
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <40CEDECA.9040600@cschneid.com>
Date: Tue, 15 Jun 2004 13:34:34 +0200
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040114
MIME-Version: 1.0
To: mike@php.net
Cc: internals@lists.php.net
References: <20040615112747.27402.qmail@pb1.pair.com>
In-Reply-To: <20040615112747.27402.qmail@pb1.pair.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: ClassHints and NULL
From: cschneid@cschneid.com (Christian Schneider)

Michael Wallner wrote:
> Is there *ANY* serious reason why NULL is not allowed in place
> of an object?  PHP will become *really* odd if this is the way
> it goes. People won't stick to this new feature...

There was a (very) long discussion about this on this mailing list a 
couple of weeks ago, please check the archive. It was decided to leave 
it the way it is for now.

> Also, these errors are hard to track because they refer to
> the line number where the function definition is, not where 
> the actual violation was comitted.

This is a good point and the same applies to the "Missing argument" 
error message. Best would be if both lines are mentioned.

- Chris