Re: ClassHints and NULL
| From: | Christian Schneider | Date: | Tue, 15 Jun 2004 11:34:34 +0000 |
| Subject: | Re: ClassHints and NULL | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-10465@lists.php.net to get a copy of this message | ||
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