ID:          37281
 Updated by:  [EMAIL PROTECTED]
 Reported By: kprice at gmail dot com
-Status:      Open
+Status:      Feedback
-Bug Type:    Documentation problem
+Bug Type:    Date/time related
-PHP Version: Irrelevant
+PHP Version: ?
 New Comment:

Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves. 

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external 
resources such as databases, etc.

If possible, make the script source available online and provide
an URL to it here. Try to avoid embedding huge scripts into the report.

Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves. 

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external 
resources such as databases, etc.

If possible, make the script source available online and provide
an URL to it here. Try to avoid embedding huge scripts into the
report.

Please also tell what your system is.


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

[2006-05-02 18:39:10] kprice at gmail dot com

Description:
------------
The documentation claims: "On systems where time_t is a 32bit signed
integer, as most common today, the valid range for year is somewhere
between 1901 and 2038, although this limitation is overcome as of PHP
5.1.0."

However, based on my testing this is not the case. mktime still returns
FALSE for dates outside of this range.



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


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

Reply via email to