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

Support fine-grained visibility in printf.c #63

Open
eyalroz opened this issue Nov 22, 2021 · 0 comments
Open

Support fine-grained visibility in printf.c #63

eyalroz opened this issue Nov 22, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@eyalroz
Copy link
Owner

eyalroz commented Nov 22, 2021

By default, the API (defined in the README) is visible out of printf.c (and exposed in printf.h), and auxiliary functions are invisible (static). However, it is conceivable that users of this library may want:

  • Everything static - for the case of #include "printf.c".
  • the default described above
  • Everything visible (extern) - when writing printf-ish code which can stand to use our innards (for some reason...)

we could support this, e.g. similarly to how nanoprintf does.
@eyalroz eyalroz added the enhancement New feature or request label Nov 22, 2021
kuba2k2 pushed a commit to libretiny-eu/library-printf that referenced this issue Feb 25, 2023
Fixes eyalroz#63; (may) improve support for systems where the null po…
e4baa6a 
…inter representation is no all-0-bits.

* "splits" behavior of pointers and hash-marked base-16 values w.r.t the `0x` prefix (although you won't see the difference unless you un-special-case the handling of 0-valued pointer).
* Passing a null pointer for an `%s` now results in `(null)`.
* Added some relevant test suite assertions involving null/0 pointers as `%s` arguments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eyalroz