>>18 >>17 can hardly be called a troll. It's creative, but it's obviously not meant for any particular purpose. Even if it was, there's no clear intent to cause the reader to react in a specific way, unless you wanted to conjecture that >>17 was making fun of C programmers. Dubious link at best.
Name:
Anonymous2009-05-16 3:02
The stdio bit shifting overload voodoo is really funky to work with and gets out of hand quickly. It is easier to look back and read a printf statement and it is easier to hold printf output strings in resource or definition files.
Name:
Anonymous2009-05-16 3:11
i use printf in c++
Name:
Anonymous2009-05-16 3:16
I much prefer printf, but it's hardly scalable because the service space is large, distributed, heterogeneous, volatile, and highly dynamic. This problem is aggravated by the added degree of dynamism, unpredictability, and distribution of programmers. Existing techniques such as EDI, component-based E-commerce systems (e.g., integrated electronic catalogs and cross-organizational workflows) are usually appropriate to integrate small number of e-services with static relationships. However, they are ineffective in large and highly dynamic environments.
The ability to display data consistantly is VERY hepful.
When you start doing things like error logging you want to show raw data and the ability to force a common format is a big +
In Win32 programming.. if you cout an HRESULT you'll get some useless integer that you'd have to convert to hex before knowing what it actually was trying to tell you. Using printf you can format it as 0x0000000 format which is much easier to read and compare in define files.
Name:
Anonymous2009-05-17 3:21
cout == printf
scanf >> cin
Name:
Anonymous2009-05-17 7:40
>>24
Yes you can. cout << hex << showbase << setfill('0') << setw(8) << n << endl;