-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why is offset typed as "chrono_t long _offset" ? #20
Comments
Probably an error. I am surprised the compiler did not pick it up as a warning... |
In fact, I think it creates an unsigned long long int which is probably something like a 64 bits integer :-P |
It is possible that what was meant originally here was to have a signed long integer in order to be able to add a negative offset. Is this something that would be needed? |
Looking back at the code ... I'm not even sure we need to have a separate variable offset to manage offsets, cause we might be able to do everything with the _startTime variable. I'll look into it. |
…ions) and fixes the chrono_t long _offset problem (closes #20).
Seems like a mistake. It should just be "chrono_t" (?)
The text was updated successfully, but these errors were encountered: