> Many functions return FALSE if something goes wrong/data has been
> exhausted/the function does not find what the developer was looking
> for.
>
> In fact, we'd have to mark a great number of functions in the manual
> "mixed" if we followed the convention you propose. Instead, we mark
> return v
ID: 38337
Updated by: [EMAIL PROTECTED]
Reported By: z_rules55 at hotmail dot com
-Status: Open
+Status: Bogus
Bug Type:Documentation problem
PHP Version: Irrelevant
New Comment:
Many functions return FALSE if something goes wrong/data has been
exhausted/the function
ID: 38338
Updated by: [EMAIL PROTECTED]
Reported By: thisgenericname at gmail dot com
-Status: Feedback
+Status: Bogus
Bug Type: Documentation problem
Operating System: Irrelevant
PHP Version: Irrelevant
New Comment:
Actually, it's c
ID: 38338
Updated by: [EMAIL PROTECTED]
Reported By: thisgenericname at gmail dot com
-Status: Open
+Status: Feedback
Bug Type: Documentation problem
Operating System: Irrelevant
PHP Version: Irrelevant
New Comment:
The changelog fil
From: z_rules55 at hotmail dot com
Operating system:
PHP version: Irrelevant
PHP Bug Type: Documentation problem
Bug description: explode function's return value is incorrect
Description:
explode() is listed as returning an array. However, its documentation
stat
From: thisgenericname at gmail dot com
Operating system: Irrelevant
PHP version: Irrelevant
PHP Bug Type: Documentation problem
Bug description: Suggestion: Include changelog with binary & snapshot builds
Description:
(would post as a Feature Request, but "[That]