Super pi days
-
In just a few years we will have: 3/14/15 9:26:53.58 and 16 years later: 31/4/15 9:26:53.58 - which in the US will also be Income Taxes due Day X|
Steve _________________ I C(++) therefore I am
-
In just a few years we will have: 3/14/15 9:26:53.58 and 16 years later: 31/4/15 9:26:53.58 - which in the US will also be Income Taxes due Day X|
Steve _________________ I C(++) therefore I am
-
Steve, I hope you get your taxes in before April 31st.
"I have a theory that the truth is never told during the nine-to-five hours. " — Hunter S. Thompson
yy/mm/dd ;P
Steve _________________ I C(++) therefore I am
-
yy/mm/dd ;P
Steve _________________ I C(++) therefore I am
-
In just a few years we will have: 3/14/15 9:26:53.58 and 16 years later: 31/4/15 9:26:53.58 - which in the US will also be Income Taxes due Day X|
Steve _________________ I C(++) therefore I am
Steve Mayfield wrote:
3/14/15
Steve Mayfield wrote:
16 years later: 31/4/15
OK, US dates with their ridiculous ordering of units has always done my head in, but I now offocially give up. How is 14 Mar 2015 (or is that 3 (Jan++)++ 2015?) 16 years behind 31 Apr 2015? Oh, you mean 15 Apr 2031? :doh: This is why is should be a flogging offense not not have dates formatted unambigously. small->large, or (full digits) large -> small, or dd MMM yyyy is even better.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
Steve Mayfield wrote:
3/14/15
Steve Mayfield wrote:
16 years later: 31/4/15
OK, US dates with their ridiculous ordering of units has always done my head in, but I now offocially give up. How is 14 Mar 2015 (or is that 3 (Jan++)++ 2015?) 16 years behind 31 Apr 2015? Oh, you mean 15 Apr 2031? :doh: This is why is should be a flogging offense not not have dates formatted unambigously. small->large, or (full digits) large -> small, or dd MMM yyyy is even better.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Yes, yyyymmdd is the easiest to sort (date treated as an integer number) and mmddyyyy or ddmmyyyy is much more difficult :sigh: - In a Genealogy course I took in college we were told to write dates at dd-MMM-yyyy so there is no ambiguity :thumbsup: ... but then us Math guys are notorious for fiddling with the digits to get the desired results ;)
Steve _________________ I C(++) therefore I am
-
Steve Mayfield wrote:
3/14/15
Steve Mayfield wrote:
16 years later: 31/4/15
OK, US dates with their ridiculous ordering of units has always done my head in, but I now offocially give up. How is 14 Mar 2015 (or is that 3 (Jan++)++ 2015?) 16 years behind 31 Apr 2015? Oh, you mean 15 Apr 2031? :doh: This is why is should be a flogging offense not not have dates formatted unambigously. small->large, or (full digits) large -> small, or dd MMM yyyy is even better.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Chris Maunder wrote:
This is why is should be a flogging offense not not have
Congratulations on a new entry into the Maunder Dictionary. :)
-
Steve Mayfield wrote:
3/14/15
Steve Mayfield wrote:
16 years later: 31/4/15
OK, US dates with their ridiculous ordering of units has always done my head in, but I now offocially give up. How is 14 Mar 2015 (or is that 3 (Jan++)++ 2015?) 16 years behind 31 Apr 2015? Oh, you mean 15 Apr 2031? :doh: This is why is should be a flogging offense not not have dates formatted unambigously. small->large, or (full digits) large -> small, or dd MMM yyyy is even better.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Chris Maunder wrote:
How is 14 Mar 2015 (or is that 3 (Jan++)++ 2015?) 16 years behind 31 Apr 2015?
Not to say that April does not have a 31st day.
Regards, Nish
My technology blog: voidnish.wordpress.com
-
Steve Mayfield wrote:
3/14/15
Steve Mayfield wrote:
16 years later: 31/4/15
OK, US dates with their ridiculous ordering of units has always done my head in, but I now offocially give up. How is 14 Mar 2015 (or is that 3 (Jan++)++ 2015?) 16 years behind 31 Apr 2015? Oh, you mean 15 Apr 2031? :doh: This is why is should be a flogging offense not not have dates formatted unambigously. small->large, or (full digits) large -> small, or dd MMM yyyy is even better.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
I wonder why we just not count the days, how difficult it may be? For example today is 734456 AD. And of course the negative numbers will represent BC.
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
-
I wonder why we just not count the days, how difficult it may be? For example today is 734456 AD. And of course the negative numbers will represent BC.
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
Or do it like StarTrek. "Stardate - 2012.20738"
-
Steve Mayfield wrote:
3/14/15
Steve Mayfield wrote:
16 years later: 31/4/15
OK, US dates with their ridiculous ordering of units has always done my head in, but I now offocially give up. How is 14 Mar 2015 (or is that 3 (Jan++)++ 2015?) 16 years behind 31 Apr 2015? Oh, you mean 15 Apr 2031? :doh: This is why is should be a flogging offense not not have dates formatted unambigously. small->large, or (full digits) large -> small, or dd MMM yyyy is even better.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Chris Maunder wrote:
How is 14 Mar 2015 (or is that 3 (Jan++)++ 2015?) 16 years behind 31 Apr 2015?
Just bag all that. Track all time values in Ticks. It's clearly the best solution, no formatting worries there. :thumbsup:
Kill some time, play my game Hop Cheops[^]
-
I wonder why we just not count the days, how difficult it may be? For example today is 734456 AD. And of course the negative numbers will represent BC.
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
Why not seconds? Right now is something like 63,456,998,400 AD. :)
-
Yes, yyyymmdd is the easiest to sort (date treated as an integer number) and mmddyyyy or ddmmyyyy is much more difficult :sigh: - In a Genealogy course I took in college we were told to write dates at dd-MMM-yyyy so there is no ambiguity :thumbsup: ... but then us Math guys are notorious for fiddling with the digits to get the desired results ;)
Steve _________________ I C(++) therefore I am
Hey - don't confuse us mathematicians with those statisticians
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
Chris Maunder wrote:
How is 14 Mar 2015 (or is that 3 (Jan++)++ 2015?) 16 years behind 31 Apr 2015?
Not to say that April does not have a 31st day.
Regards, Nish
My technology blog: voidnish.wordpress.com
If the US wants to biggie-size April then it's not something that would surprise me
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
Steve Mayfield wrote:
3/14/15
Steve Mayfield wrote:
16 years later: 31/4/15
OK, US dates with their ridiculous ordering of units has always done my head in, but I now offocially give up. How is 14 Mar 2015 (or is that 3 (Jan++)++ 2015?) 16 years behind 31 Apr 2015? Oh, you mean 15 Apr 2031? :doh: This is why is should be a flogging offense not not have dates formatted unambigously. small->large, or (full digits) large -> small, or dd MMM yyyy is even better.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
In my workplace, we use yyyymmdd for comments, file naming, etc.. it's damn easy to sort. I have always felt that mmddyy is just irrational. You don't say a player finished a race in 23 mins 45 secs 1 hour. That's just ridiculous.
Peace, ye fat guts!
Perhaps what we need is to use the 'Time Police'. They could rigorously enforce stamdards across the world. Nay even acroos TIME itself. Question is do we A) Create the Time Police ourselves or B) Wait for their creation in the future. With Time Travel they cna travel back to our 'time' to Retro Enforce Time Standards Regrads The Retro-Enforcer
-
Yes, yyyymmdd is the easiest to sort (date treated as an integer number) and mmddyyyy or ddmmyyyy is much more difficult :sigh: - In a Genealogy course I took in college we were told to write dates at dd-MMM-yyyy so there is no ambiguity :thumbsup: ... but then us Math guys are notorious for fiddling with the digits to get the desired results ;)
Steve _________________ I C(++) therefore I am
Read the discussions on date micro formats for HTML5 (sorry, I haven't got a link - I am sure that another CPian will be able to find some). Genealogies is cited as a difficult case as the dates go before 1752. The recommendation (in the microformats discussions) is that you still use the Gregorian dates, but that would be very confusing as the historical dates were Julian (which I am sure is what most genealogy courses would use). Also, genealogies hit one of the other date format 'gotchas': approximations; how do you represent 'sometime probably in September between 4BC and 1AD'?
-
In my workplace, we use yyyymmdd for comments, file naming, etc.. it's damn easy to sort. I have always felt that mmddyy is just irrational. You don't say a player finished a race in 23 mins 45 secs 1 hour. That's just ridiculous.
Peace, ye fat guts!
krumia wrote:
You don't say a player finished a race in 23 mins 45 secs 1 hour
No you don't. But it is more common to say "It is ten past eleven", than to say "It is 11 o'clock plus ten minutes". Admittedly, "It is 11:10" is quicker. Posted just after ten past eleven, GMT.
-
In just a few years we will have: 3/14/15 9:26:53.58 and 16 years later: 31/4/15 9:26:53.58 - which in the US will also be Income Taxes due Day X|
Steve _________________ I C(++) therefore I am
Pi is Wrong! :) Couldn't resist...
-
In just a few years we will have: 3/14/15 9:26:53.58 and 16 years later: 31/4/15 9:26:53.58 - which in the US will also be Income Taxes due Day X|
Steve _________________ I C(++) therefore I am