If not for this problem, does printf satisfy our requirements or are
there
any other problems with it? If it's OK, maybe we could just include
the
"standard" printf right into our codebase, instead of linking to a
library?
Just an idea.
Possibly, but if we do one ourselves we can be more clever with e.g. rounding behavior. Anyway, Bryce said he alraedy had some code somewhere, as I recall...
Yes, I do. I've added a task for myself to add this to the codebase.
The reason I ask this questions is because I see how Lauris is handling this in 0.33. Now instead of a single printf call, he declares a char[] buffer for each value, calls a custom conversion function, and then assembles these buffers into a string. That is extremely bulky and hard to read, and I would like to avoid this if possible, preserving the format string approach of printf. So, how close is your code to being a drop-in replacement for printf with its format strings?
_________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2f...