forked from mpaland/printf
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Don't always alias #14
Comments
eyalroz
pushed a commit
that referenced
this issue
Jul 9, 2021
…d value, controlling whether or not to alias `printf()`, `sprintf()` etc.
eyalroz
pushed a commit
that referenced
this issue
Jul 11, 2021
…d value, controlling whether or not to alias `printf()`, `sprintf()` etc.
eyalroz
pushed a commit
that referenced
this issue
Jul 14, 2021
…d value, controlling whether or not to alias `printf()`, `sprintf()` etc.
eyalroz
pushed a commit
that referenced
this issue
Jul 14, 2021
…d value, controlling whether or not to alias `printf()`, `sprintf()` etc.
eyalroz
pushed a commit
that referenced
this issue
Jul 30, 2021
…d value, controlling whether or not to alias `printf()`, `sprintf()` etc.
eyalroz
pushed a commit
that referenced
this issue
Jul 30, 2021
…d value, controlling whether or not to alias `printf()`, `sprintf()` etc.
eyalroz
pushed a commit
that referenced
this issue
Aug 3, 2021
…d value, controlling whether or not to alias `printf()`, `sprintf()` etc.
eyalroz
added a commit
that referenced
this issue
Sep 27, 2021
…leave their names as macros outside the library - that's not such a great idea.
eyalroz
added a commit
that referenced
this issue
Sep 27, 2021
…leave their names as macros outside the library - that's not such a great idea.
eyalroz
added a commit
that referenced
this issue
Nov 8, 2021
eyalroz
added a commit
that referenced
this issue
Nov 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment, the library always aliases printf, sprintf, vsprintf etc. This is problematic, because you might want to use it alongside the standard library's
<stdio.h>
(whether because you're using the standard library as well, or because you're including another header which itself pulls<stdio.h>
without you really needing it).So, we should have a CMake option controlling whether or not this is done.
The text was updated successfully, but these errors were encountered: