forked from mpaland/printf
-
Notifications
You must be signed in to change notification settings - Fork 55
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
Call vfoo_ from foo_ functions #88
Labels
resolved-on-develop
A changeset fixing this issue has been commiutted to the development branch
task
Comments
eyalroz
added a commit
that referenced
this issue
Jan 22, 2022
…list corresponding functions rather than directly calling `_vnsprintf()` - reducing some code duplication.
eyalroz
added a commit
that referenced
this issue
Jan 26, 2022
…list corresponding functions rather than directly calling `_vnsprintf()` - reducing some code duplication.
eyalroz
added a commit
that referenced
this issue
Jan 31, 2022
…list corresponding functions rather than directly calling `_vnsprintf()` - reducing some code duplication.
eyalroz
added a commit
that referenced
this issue
Jan 31, 2022
…list corresponding functions rather than directly calling `_vnsprintf()` - reducing some code duplication.
eyalroz
added a commit
that referenced
this issue
Jan 31, 2022
…list corresponding functions rather than directly calling `_vnsprintf()` - reducing some code duplication.
eyalroz
added a commit
that referenced
this issue
Feb 11, 2022
…list corresponding functions rather than directly calling `_vnsprintf()` - reducing some code duplication.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
resolved-on-develop
A changeset fixing this issue has been commiutted to the development branch
task
Instead of calling
_vsnprintf()
directly from eachfoo_()
function, let's callvfoo_()
. This will avoid a tiny bit of code duplication now; but soon will probably avoid a little more code duplication - due to a planned fix for #87 .The text was updated successfully, but these errors were encountered: