#22282 [Opn->Csd]: function synopsis for dba_fetch() is wrong
| From: | philip@php.net | Date: | Fri, 18 Jul 2003 20:04:28 +0000 |
| Subject: | #22282 [Opn->Csd]: function synopsis for dba_fetch() is wrong | ||
| References: | 1 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969355363@lists.php.net to get a copy of this message | ||
ID: 22282
Updated by: philip@php.net
Reported By: helly@php.net
-Status: Open
+Status: Closed
Bug Type: Documentation problem
Operating System: ANY
PHP Version: 4.3.0
New Comment:
This is fixed in CVS by Didou and will show up when the manual is next
built.
Status->closed.
Previous Comments:
------------------------------------------------------------------------
[2003-04-06 06:56:34] sniper@php.net
This is really a special case..if that middle option
is not used, then the function assumes that the 2nd one is the 3rd in
the proto..
------------------------------------------------------------------------
[2003-04-01 19:30:12] philip@php.net
Currently it's not possible but really it just seems odd, optional
parameters should be to the right.
------------------------------------------------------------------------
[2003-04-01 18:08:10] alindeman@php.net
According to funcsummary.txt in phpdoc/, this is the function layout
string dba_fetch(string key, [int skip ,] int handle)
Fetches the data associated with key
Is this possible to implement in the documentation without making the
third param optional?
------------------------------------------------------------------------
[2003-04-01 17:49:52] philip@php.net
See:
http://cvs.php.net/cvs.php/phpdoc/en/reference/dba/functions/dba-fetch.xml
Hasn't been touched in four months while the manual was last built two
months ago, reopening...
Although personally I don't understand how a middle parameter can be
optional...
------------------------------------------------------------------------
[2003-04-01 17:27:34] alindeman@php.net
If it's fixed in the XML file, the documentation probably hasn't
updated (there has been some problem with that lately). Should be
fixed when documentation starts updating again...
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/22282
--
Edit this bug report at http://bugs.php.net/?id=22282&edit=1