What is the benefit in getting the current time this way as opposed to using System.currentTimeInMillis()

Asked Aug 16 '12 at 07:31

Active Aug 16 '12 at 07:31

Viewed 90 times

Possible Duplicate:
System.currentTimeMillis() vs. new Date() vs. Calendar.getInstance().getTime()

I have just come across this in some legacy code:

GregorianCalendar.getInstance().getTime().getTime()

This just seems like a very circuitous way of calling System.currentTimeInMillis().

The server that this code runs on is probably running in a timezone other than UTC, but looking at the source of Date.getTime() everything will be GMT-based anyway (yes, I know that GMT doesn't precisely equal UTC).

Could there be a benefit I'm not aware of?

edited May 23 '17 at 12:20

Community

asked Aug 16 '12 at 07:31

Rich

15,602
15
79
126

8

check http://stackoverflow.com/questions/368094/system-currenttimemillis-vs-new-date-vs-calendar-getinstance-gettime – Nandkumar Tekale Aug 16 '12 at 07:34
1

also check this http://stackoverflow.com/questions/11960082/is-calendar-getinstance-gettime-ever-going-to-give-me-a-different-answer-tha/11960343#11960343. Not sure but helpful. – Nandkumar Tekale Aug 16 '12 at 07:47
Thanks for the links - I've voted to close my question - feel free to do the same! – Rich Aug 16 '12 at 07:51
I can't, more +101 to go to close. :) – Nandkumar Tekale Aug 16 '12 at 07:55

What is the benefit in getting the current time this way as opposed to using System.currentTimeInMillis()

0 Answers0