Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Clarify behavior of "%zi" #46

Closed
eyalroz opened this issue Sep 22, 2021 · 0 comments
Closed

Clarify behavior of "%zi" #46

eyalroz opened this issue Sep 22, 2021 · 0 comments
Assignees
@eyalroz
Labels
resolved-on-develop A changeset fixing this issue has been commiutted to the development branch task

Comments

@eyalroz
Copy link
Owner

eyalroz commented Sep 22, 2021

The C99 standard is vague about what exactly one is to pass for the "%zi" format specifier - it's a "signed size_t" - but that's not properly defined. We need to be explicit about what we expect for this specifier, so as not to confuse users.
@eyalroz eyalroz added the task label Sep 22, 2021
@eyalroz eyalroz mentioned this issue Sep 22, 2021
Closed
@eyalroz eyalroz self-assigned this Sep 25, 2021
eyalroz added a commit that referenced this issue Sep 25, 2021
@eyalroz
Fixes #46: Added some build-time checks ensuring our "%zi" behavior…
d9a6301 
… is valid, and a clarification comment in `README.md`.
@eyalroz eyalroz added the resolved-on-develop A changeset fixing this issue has been commiutted to the development branch label Sep 25, 2021
eyalroz added a commit that referenced this issue Sep 27, 2021
@eyalroz
Fixes #46: Added some build-time checks ensuring our "%zi" behavior…
ae105ac 
… is valid, and a clarification comment in `README.md`.
@eyalroz eyalroz closed this as completed Oct 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eyalroz eyalroz

Labels
resolved-on-develop A changeset fixing this issue has been commiutted to the development branch task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eyalroz