Re: Re: cvs: ZendEngine2 / zend_builtin_functions.c /tests 009.phpt php-src/ext/reflection/tests 027.phpt php-src/ext/standard/tests/class_object
get_class_error_001.phpt get_class_variation_001.phpt
| From: | Paul Biggar | Date: | Mon, 16 Mar 2009 18:39:50 +0000 |
| Subject: | Re: Re: cvs: ZendEngine2 / zend_builtin_functions.c /tests 009.phpt php-src/ext/reflection/tests 027.phpt php-src/ext/standard/tests/class_object get_class_error_001.phpt get_class_variation_001.phpt |
||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-43373@lists.php.net to get a copy of this message | ||
2009/3/16 Johannes Schlüter <johannes@php.net>:
> On Mon, 2009-03-16 at 18:41 +0100, Pierre Joye wrote:
>> >> Usually we return NULL in case parameter parsing fails, this is
>> >> documented like this:
> The documentation is just like with other functions returning NULL for
> param parsing and false for other errors. While browsing a bit through
> the docs I couldn't find any function mentioning "Returns NULL in case
> parameter parsing fails" even though most functions do.
Why do functions return NULL? (I know the technical answer, obviously,
I'm interested in the design decision). If FALSE is the error
condition, whats the point in a separate NULL error condition?
Paul
--
Paul Biggar
paul.biggar@gmail.com