[vtkusers] vtkTimeStamp::Modified() unsigned long overflow

[Biddiscombe, John A.]

oops, didn't cc list 

> -----Original Message-----
> From: Biddiscombe, John A.
> Sent: 24 September 2013 12:54
> To: 'Wim Koomen'
> Subject: RE: [vtkusers] vtkTimeStamp::Modified() unsigned long overflow
> 
> Wim
> 
> > My questions:
> > - Is the documentation making a wrong statement here?
> > - To mitigate this problem, wouldn't it be good idea to change the
> > vtkTimeStamp unsigned long to a guaranteed 64bit value?
> 
> Yes, the documentation is wrong.
> 
> Yes, a 64 bit value should be used instead.
> 
> I have no idea if it can be fixed by time changing the type in vtkTimeStamp, or
> if there are places in the code that make local stores of the time and use
> int/longs anywhere. Probably using vtkTypeInt64 in vtkTimeStamp will fix
> most cases and then the compiler might throw some warning about types
> losing precision which could be checked afterwards...
> 
> JB