#38130 [Opn]: Unwritten rule on functions returning null

ID: 38130 User updated by: btherl at yahoo dot com dot au Reported By: btherl at yahoo dot com dot au Status: Open Bug Type: Documentation problem Operating System: Linux PHP Version: Irrelevant New Comment: The origin of this report was when I suggested that a function document that it returns NULL when arguments are incorrectly typed. The response I got was "Most functions return NULL on bogus parameters. No need to waste time with this." Which leads to the obvious question: If there is no need to document that function X returns NULL on bogus parameters, then where is it documented? How about this: "The return value of built-in functions is undefined when the parameters are not of the correct type. Most functions will return NULL, but this is just a convention, and cannot be relied on." Anyone who wishes to reply with "This is a waste of time", save your time and don't hit submit :) I'm not writing this for you. Previous Comments: ------------------------------------------------------------------------ [2006-07-18 10:59:36] colder@php.net "most functions" : Returning NULL is not a general rule, thus it shoulnd't IMO be documented globally such as in the docs for NULL. ------------------------------------------------------------------------ [2006-07-18 10:12:05] btherl at yahoo dot com dot au Description: ------------ Most functions return NULL if their arguments are invalid. This should be documented somewhere, perhaps in "Internal (built-in) functions". It may be useful to document it in the documentation for NULL itself. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=38130&edit=1