Time + 10 minutes

[Krustov]

$ganja=date("D dS M h:i A");
Assuming the above produced the following .

Tue 02nd Jan 11:55 PM
How do i add 10 minutes to it to produce this ? .

Wed 03rd Jan 00:05 AM

[Geoff Berrow]

Message-ID: <MP************************@news.newsreader.comfro m
Krustov contained the following:

>$ganja=date("D dS M h:i A");
Assuming the above produced the following .

Tue 02nd Jan 11:55 PM

It would produce the current time

>

How do i add 10 minutes to it to produce this ? .

Wed 03rd Jan 00:05 AM

$ganja=date("D dS M h:i A",time()+600);

--
Geoff Berrow (put thecat out to email)
It's only Usenet, no one dies.
My opinions, not the committee's, mine.
Simple RFDs http://www.ckdog.co.uk/rfdmaker/

[Krustov]

<comp.lang.php>
<Geoff Berrow>
<Thu, 04 Jan 2007 17:18:20 +0000>
<ke********************************@4ax.com>

$ganja=date("D dS M h:i A",time()+600);

That worked fine - thanks to both users .
--
www.phptakeaway.co.uk
(work in progress)

[Moot]

Krustov wrote:

$ganja=date("D dS M h:i A",time()+600);

That worked fine - thanks to both users .

Or, if you're like me and don't want to figure out the correct number
to add for various intervals, a more plain-english style solution would
be:
$ganja = date("D dS M h:i A",strtotime("+10 minutes"));

[Rik]

David Gillen wrote:

Moot said:

>Krustov wrote:

>>>$ganja=date("D dS M h:i A",time()+600);
That worked fine - thanks to both users .

Or, if you're like me and don't want to figure out the correct number
to add for various intervals, a more plain-english style solution
would be:
$ganja = date("D dS M h:i A",strtotime("+10 minutes"));

Haha, I like that. Anything that makes something easier to understand
when scanning the code is good.

Well strtotime has it's advantages. However, it's poorly documented and
sometimes unpredictable. After a short while I reverted back to working
with adding/subtracting timestamps, just with a comment in the code beside
it. Equally (or even more) clear thans to the comment, and 100%
predictable.
--
Rik Wasmus

[Geoff Berrow]

Message-ID: <cd***************************@news2.tudelft.nlfro m Rik
contained the following:

>>$ganja = date("D dS M h:i A",strtotime("+10 minutes"));

Haha, I like that. Anything that makes something easier to understand
when scanning the code is good.

Well strtotime has it's advantages. However, it's poorly documented and
sometimes unpredictable. After a short while I reverted back to working
with adding/subtracting timestamps, just with a comment in the code beside
it. Equally (or even more) clear thans to the comment, and 100%
predictable.

I've had the same experience. And if you really can't work out the
number of seconds in ten minutes, let the code do the work

$ganja=date("D dS M h:i A",time()+(60*10));

Personally though I'd rather keep things that I may want to change
elsewhere, so:

$delay=600;
//this can be in a config file and commented
....
$ganja=date("D dS M h:i A",time()+$delay);

--
Geoff Berrow (put thecat out to email)
It's only Usenet, no one dies.
My opinions, not the committee's, mine.
Simple RFDs http://www.ckdog.co.uk/rfdmaker/

[Michael Fesser]

..oO(Rik)

>Well strtotime has it's advantages. However, it's poorly documented and
sometimes unpredictable. After a short while I reverted back to working
with adding/subtracting timestamps, just with a comment in the code beside
it. Equally (or even more) clear thans to the comment, and 100%
predictable.

Yep, but in some cases you have to be very careful when doing date/time
calculations by hand. Daylight saving time can be an issue for example.

Micha

[Moot]

Rik wrote:

David Gillen wrote:

Moot said:

Krustov wrote:
$ganja=date("D dS M h:i A",time()+600);
That worked fine - thanks to both users .
Or, if you're like me and don't want to figure out the correct number
to add for various intervals, a more plain-english style solution
would be:
$ganja = date("D dS M h:i A",strtotime("+10 minutes"));

Haha, I like that. Anything that makes something easier to understand
when scanning the code is good.

Well strtotime has it's advantages. However, it's poorly documented and
sometimes unpredictable. After a short while I reverted back to working
with adding/subtracting timestamps, just with a comment in the code beside
it. Equally (or even more) clear thans to the comment, and 100%
predictable.
--
Rik Wasmus

Agreed. strtotime has some annoying flaws that aren't officially
documented. For an illustration, try the following code:
<?php
echo date('m/d/Y', strtotime('3/31/2006')) . " - Today\n";
echo date('m/d/Y', strtotime('-1 month', strtotime("3/31/2006"))) . " -
Last Month (expect: 2/??/2006)\n";
echo date('m/d/Y', strtotime('+1 month', strtotime("3/31/2006"))) . " -
Next Month (expect: 4/??/2006)\n";
?>

This example shows how strtotime's handling of months could really
screw up logic expecting it to work in a different way than it actually
does (I should know, I've learned it the hard way). Since there are 28
days in Feb, strtotime adds the 3 extra days (to 31) and ends up at
March 3rd, similar problem with April, which has 30 days, so the extra
1 puts it to May 1st.

I've only really had a problem with strtotime with months, though.
Most other time intervals seem to work as expected.

- Moot

[Michael Fesser]

..oO(Moot)

>Agreed. strtotime has some annoying flaws that aren't officially
documented. For an illustration, try the following code:
[...]

This example shows how strtotime's handling of months could really
screw up logic expecting it to work in a different way than it actually
does (I should know, I've learned it the hard way). Since there are 28
days in Feb, strtotime adds the 3 extra days (to 31) and ends up at
March 3rd, similar problem with April, which has 30 days, so the extra
1 puts it to May 1st.

This behaviour is documented:

| The fuzz in units can cause problems with relative items. For example,
| `2003-07-31 -1 month' might evaluate to 2003-07-01, because 2003-06-31
| is an invalid date. To determine the previous month more reliably, you
| can ask for the month before the 15th of the current month. [...]

http://www.gnu.org/software/tar/manu...15.html#SEC115

Micha

[Rik]

Michael Fesser wrote:

.oO(Moot)

>Agreed. strtotime has some annoying flaws that aren't officially
documented. For an illustration, try the following code:
[...]

This example shows how strtotime's handling of months could really
screw up logic expecting it to work in a different way than it
actually does (I should know, I've learned it the hard way). Since
there are 28 days in Feb, strtotime adds the 3 extra days (to 31)
and ends up at March 3rd, similar problem with April, which has 30
days, so the extra 1 puts it to May 1st.

This behaviour is documented:

>The fuzz in units can cause problems with relative items. For
example, `2003-07-31 -1 month' might evaluate to 2003-07-01, because
2003-06-31 is an invalid date. To determine the previous month more
reliably, you can ask for the month before the 15th of the current
month. [...]

http://www.gnu.org/software/tar/manu...15.html#SEC115

Yup, this is actually not one of the things I would qualify as
unpredictable behviour, yet it's understandable that with a syntax like
strtotime people understand it to work.

In the same ballpark of unexpected yet highly logical behaviour:

echo date('r',mktime(0,0,0,0,0,2007));

Unexpected for most, but highly logical nonetheless ;)
--
Rik Wasmus

[Michael Fesser]

..oO(Rik)

>In the same ballpark of unexpected yet highly logical behaviour:

echo date('r',mktime(0,0,0,0,0,2007));

Unexpected for most, but highly logical nonetheless ;)

Nice example. ;)

Micha

PS: But still documented ... SCNR