ID:               37486
 Updated by:       [EMAIL PROTECTED]
 Reported By:      brianm-phpbugs at dealnews dot com
-Status:           Assigned
+Status:           Closed
 Bug Type:         Documentation problem
 Operating System: Linux
 PHP Version:      Irrelevant
 Assigned To:      philip
 New Comment:

This is now [finally] documented in CVS and will show up after the next
manual build, thanks for reporting the bug :)

See the diff/info here:
http://news.php.net/php.doc/969373952
http://news.php.net/php.doc/969373953


Previous Comments:
------------------------------------------------------------------------

[2006-05-18 18:15:12] [EMAIL PROTECTED]

This error came about in PHP 5.1.0

------------------------------------------------------------------------

[2006-05-18 16:29:30] [EMAIL PROTECTED]

Whether E_STRICT is in E_ALL does not relate to this bug, this function
emits E_STRICT regardless. And since we document future releases,
including PHP 6, it's still a valid bug. Or wait, maybe it's a feature
request until 5.2.0 is out? ;)

This bug report has been changed to include "all date functions that
result in this error" as I believe all are affected that pass in a
timestamp. If you know of one not in ref.datetime please write that
here. Assigning to self. Creating an entity to include in all such
functions. 

------------------------------------------------------------------------

[2006-05-18 12:47:01] brianm-phpbugs at dealnews dot com

E_STRICT is thrown when you set error_reporting to throw it.  And
according to the discussion on internals (of which I am a part of),
they want people to develop that way.

Mark it will fix later or whatever, but, this will need to be addressed
as E_STRICT gets more and more steam.

------------------------------------------------------------------------

[2006-05-18 12:09:24] crescentfreshpot at yahoo dot com

E_STRICT is only thrown in latest snaps, not in any official release
(f.e. not in 5.1.4). You can't expect the documentation to be _that_ up
to date.

There is a huge thread on internals going on right now on whether
E_STRICT should be triggered for this sort of thing (i.e. when E_ALL is
set) in the next release.

This is not a doc bug. Not yet at least ;)

------------------------------------------------------------------------

[2006-05-18 06:02:39] [EMAIL PROTECTED]

We need a script to check all of php-src (and PECL) for what functions
may emits errors, and document accordingly. E_STRICT and E_WARNING
especially. In fact, it should check return types too. And compare
prototypes. Sounds like a large task so we can simply add E_STRICT info
to strftime() for now :)

------------------------------------------------------------------------

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/37486

-- 
Edit this bug report at http://bugs.php.net/?id=37486&edit=1

Reply via email to