#49754 [Opn->Bgs]: date's documentation about 'u' implies it actually works
| From: | bjori@php.net | Date: | Fri, 02 Oct 2009 19:58:11 +0000 |
| Subject: | #49754 [Opn->Bgs]: date's documentation about 'u' implies it actually works | ||
| References: | 1 | Groups: | php.doc.bugs |
| Request: | Send a blank email to doc-bugs+get-2866@lists.php.net to get a copy of this message | ||
ID: 49754
Updated by: bjori@php.net
Reported By: urkle at outoforder dot cc
-Status: Open
+Status: Bogus
Bug Type: Documentation problem
Operating System: CentOS 5
PHP Version: 5.2.11
New Comment:
Scroll a little further down and you'll see
"Note: Since this function only accepts integer timestamps the u format
character is only useful when using the date_format() function with user
based timestamps created with date_create(). "
Since all the format characters are listed on the date() page, this
will stay like this until the table can be refactored into its own
appendix.
Previous Comments:
------------------------------------------------------------------------
[2009-10-02 19:02:08] urkle at outoforder dot cc
Description:
------------
The documentation currently states.
u Microseconds (added in PHP 5.2.2) Example: 654321
which contradicts the result of bug #41806
http://bugs.php.net/bug.php?id=41806
which states that because date() only accepts an integer and uses
time() which only returns an integer the 'u' formatting option will ONLY
return 000000.
This severely limits the usefulness of having that 'u' formatting
option.
Can the documentation either be updated to reflect that it will ONLY
return '000000' OR can the date() be modified to use microtime() when
possible and to accept a float so the 'u' format option can be useful.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=49754&edit=1