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: | Johannes Schlüter | Date: | Mon, 16 Mar 2009 18:01:48 +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 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-43372@lists.php.net to get a copy of this message | ||
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:
> >
> > If all other functions return NULL with wrong args, why should get_class
> > return false? Is there any value in it besides the fact that docs say so?
>
> The main reason is the documentation. It introduces a useless BC break
> which was reported in #47664.
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.
johannes