-
Notifications
You must be signed in to change notification settings - Fork 1
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
Document the use of the V* constants for the c_cc
field
#8
Comments
I see, that makes sense, I didn’t think about that. Would you like to submit a PR? It’s only a couple of lines that you’ll have to modify. |
Sure. I can raise a PR. What do you think is a better approach to fix this?
I am leaning towards the later.. I'll also try to add an example to the documentation. |
I'm up for the latter! Thanks for offering to submit a PR! |
Merged
Thanks @kdheepak! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The use of the V* constants like
VMIN
andVTIME
isn't well documented and can lead to an off-by-one error since Julian arrays are 1-based indexed, while the constants are the same as thelibc
versions which are for 0-based indexing arrays.So doing something like this, which is very intuitive, sets the incorrect value in the struct.
The text was updated successfully, but these errors were encountered: