php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Doc Bug #66789 date() - hasn't warning if pass on second param bool or null type
Submitted: 2014-02-27 11:32 UTC Modified: 2016-06-14 16:21 UTC
Votes:1
Avg. Score:4.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:0 (0.0%)
From: e dot romanov88 at gmail dot com Assigned: cmb (profile)
Status: Not a bug Package: Documentation problem
PHP Version: 5.4.25 OS: SentOS
Private report: No CVE-ID: None
View Developer Edit
 [2014-02-27 11:32 UTC] e dot romanov88 at gmail dot com 
Description:
------------
---
From manual page: http://www.php.net/function.date
---

If a non-numeric value is used for timestamp, FALSE is returned and an E_WARNING level error is emitted. - 

date('Y-m-d H:i:s', null) or date('Y-m-d H:i:s', false) - hasn't warning, and function return reusult like date('Y-m-d H:i:s', 0);

Test script:
---------------
echo date('Y-m-d H:i:s', null);

Expected result:
----------------
PHP Warning:  date() expects parameter 2 to be long, null given.

Actual result:
--------------
"1970-01-01 03:00:00"

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2016-06-14 16:21 UTC] cmb@php.net
-Status: Open +Status: Not a bug -Assigned To: +Assigned To: cmb
 [2016-06-14 16:21 UTC] cmb@php.net 
That behavior is already documented for built-in functions
generally[1]:

| If the parameters given to a function are not what it expects,
| such as passing an array where a string is expected, the return
| value of the function is undefined.

It would be distracting to document this for each built-in
function explicitly.

[1] <http://php.net/manual/en/functions.internal.php>
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Sun Oct 26 15:00:01 2025 UTC