php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Doc Bug #6928 No documentation of function parameter length restrictions
Submitted: 2000-09-28 22:21 UTC Modified: 2000-10-17 11:25 UTC
From: rbs at bu dot edu Assigned:
Status: Closed Package: Documentation problem
PHP Version: 4.0.2 OS: Any
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: rbs at bu dot edu
New email:
PHP Version: OS:

 

 [2000-09-28 22:21 UTC] rbs at bu dot 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

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2000-10-17 11:25 UTC] chagenbu@php.net
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.
 
PHP Copyright © 2001-2026 The PHP Group
All rights reserved.
Last updated: Thu Jun 18 21:00:01 2026 UTC