PHP 4.0 Bug #6928 Updated: No documentation of function parameter length restrictions
| From: | chagenbu@php.net | Date: | Tue, 17 Oct 2000 15:25:20 +0000 |
| Subject: | PHP 4.0 Bug #6928 Updated: No documentation of function parameter length restrictions | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-35266@lists.php.net to get a copy of this message | ||
ID: 6928
Updated by: chagenbu
Reported By: rbs@bu.edu
Status: Closed
Bug Type: Documentation problem
Assigned To:
Comments:
This is a gross generalization from a single problem. If there are any length restrictions which can
not be worked around in the source code, they should be documented - but I'm not aware of any
of those. The problem with imap_open is being fixed. Any others should be fixed at the source. We
shouldn't document broken behavior.
Previous Comments:
---------------------------------------------------------------------------
[2000-09-28 22:21:42] rbs@bu.edu
Upon encountering a Segv problem in PHP and examining the PHP source code, it became apparent that
there is a big, conspicuous omission in the documentation of PHP functions: the acceptable length of
function operands. Various PHP functions (e.g., imap_open()) actually copy given strings to
fixed-length storage areas. There is thus a definite reality limit on the length of what the PHP
user can supply to PHP functions - but the PHP documentation is generally devoid of any
specification of the allowable lengths of function operands.
PHP function documentation is much too casual in this regard, and needs to more rigidly define
what the functions can and will accept. Always specify your pardigm limits.
thanks, Richard Sims, Boston University OIT
---------------------------------------------------------------------------
Full Bug description available at: http://bugs.php.net/?id=6928