|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
Timer.getFPGATimestamp() vs System.currentTimeMillis()
coming from a desktop/server Java background, I've always used System.currentTimeMillis() for elapsed time calcs, and we use it on our bot consistently.
Just noticed Timer.getFPGATimestamp(), which strikes me as *probably* being better than System.currentTimeMillis() (though the former might be using the latter for all I know). Anyone have any insight as too whether the two differ significantly? Don't want to do the rework if not significantly better (though will start with Timer.getFPGATimestamp() next year!) |
|
#2
|
||||
|
||||
|
Re: Timer.getFPGATimestamp() vs System.currentTimeMillis()
Quote:
http://www.chiefdelphi.com/forums/sh....php?p=1224866 Last edited by Ether : 13-02-2014 at 11:39. |
|
#3
|
||||
|
||||
|
Re: Timer.getFPGATimestamp() vs System.currentTimeMillis()
One difference is the resolution. Timer's method has a resolution of microseconds instead of currentTimeMillis()'s millisecond resolution.
|
|
#4
|
||||
|
||||
|
Re: Timer.getFPGATimestamp() vs System.currentTimeMillis()
thanks. I missed the difference in resolution. Not important enough to refit existing code (esp since Java TimerTasks only schedule down to the millisecond), but good to know.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|