-
Notifications
You must be signed in to change notification settings - Fork 7
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
C99 #10
Comments
I don't understand exactly what you are suggesting. My code does follow C99 standard, chosen mostly because of the significant improvements over C89 (like But what do you mean by "explicitly set[ting] C standard"? |
Sorry for not being clear. |
faelys
added a commit
that referenced
this issue
Oct 14, 2015
merci |
ghost
closed this as completed
Oct 14, 2015
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How about to explicitly set C standard to at least C99 ?
Because, for example buffer.c uses vsnprintf(), va_copy().
The function and macro conform to ISO/IEC 9899:1999 ("ISO C99").
see: http://en.cppreference.com/w/c/io/vfprintf
and http://en.cppreference.com/w/c/variadic/va_copy
The text was updated successfully, but these errors were encountered: