Christoph Bugel <chris@tti-telecom.com> writes: > On Tue 2002-01-22, Fons Rademakers wrote: > > Hi Hermann-Josef, [...] > > since there is a lot of interest for a general TTimeStamp class > > with higher precision and all conversion possibilities I would > > propose to adopt Robert Hatchers TTimeStamp class for this. > > I don't use ROOT classes, but just out of interest in the subject > I would like to add that in my view the correct (yeah, right) > solution would be a Date class that represents a point in time in > an absolute, zone-independant way (time_t will do), and it will [...] > it should probably hold a time_t plus a milisec as data members) The prcision should be at least nanoseconds, as this gives no real overhead if you consider that with more that 1 second resolution a 32Bit integer is not enough, so if you need another data member for the sub-second part you could easily go to nanoseconds, which is nowadys more than 2 CPU clock cycles. Greetings, Juergebn -- Dr. Juergen Hannappel http://lisa2.physik.uni-bonn.de/~hannappe mailto:hannappel@physik.uni-bonn.de Phone: +49 228 73 2447 FAX ... 7869 Physikalisches Institut der Uni Bonn Nussallee 12, D-53115 Bonn, Germany CERN: Phone: +412276 76461 Fax: ..77930 Bat. 892-R-A13 CH-1211 Genève 23
This archive was generated by hypermail 2b29 : Sat Jan 04 2003 - 23:50:40 MET