Re:Where the Printf Rubber Meets the Road (2010)
by MaulingMonkey on Sunday October 05, 2014 @02:50AM
(#8411645)
> You might think, but who in their right mind would redefine printf()?
One cannot discount those in their wrong mind either.
I had a header dedicated to #undef ing things ruby.h redirected so I could include it in C++ contexts without breaking the SC++L. While I don't see printf on the list, read, write, close, fclose, sleep, and many more are.
Re:Where the Printf Rubber Meets the Road (2010)
by DannyBee on Saturday October 04, 2014 @10:59PM
(#8411322)
"and not worry that printf() has been redefined by the application."
Note that GCC assumes it isn't redefined unless you use -fno-builtin-printf.
It will replace printf calls with puts and do other fun things.
You might think, but who in their right mind would redefine printf()? But C has an infinite number of people using it all the time, so every possible weird thing has been done a few times by now.