tag:blogger.com,1999:blog-17885055.post8416455013608697521..comments2009-03-03T15:51:45.090+01:00Comments on The Julipedia: Blog: Debug messages without using the C++ preprocessorJulio Merinohttp://www.blogger.com/profile/08233346614736256024noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-17885055.post-63028876101677296422009-03-03T15:51:00.000+01:002009-03-03T15:51:00.000+01:00C'mon... it's _not_ that bad...#if __LP64__# defin...C'mon... it's _not_ that bad...<BR/><BR/>#if __LP64__<BR/># define t_address_FMT "0x%016lx"<BR/>#else<BR/># define t_address_FMT "0x%016llx"<BR/>#endif<BR/><BR/>#define FMT(t) t##_FMT<BR/><BR/>fprintf(wherever, "blabla "FMT(t_address)" bleble\n", address);<BR/><BR/>*Faster* and *explicit*.<BR/><BR/>OO is not the way to go for _everything_...<BR/><BR/>apa!<BR/><BR/>PS: just waiting for C++0x to be official and have type safety on typedefs :)Lluisnoreply@blogger.comtag:blogger.com,1999:blog-17885055.post-91927725195921509592009-03-03T08:48:00.000+01:002009-03-03T08:48:00.000+01:00iostreams may not be as efficient as printf, but f...iostreams may not be as efficient as printf, but for debugging code, it does not matter; it's gonna be slow anyway.<BR/><BR/>About internationalization, that's a good point that I hadn't thought about! But then you can use formatting strings embedded in streams. Take a look at Boost.Format.<BR/><BR/>At last, about type safety, that's true, but things get very ugly when you start using custom types (aka typedefs). Then you need to define ugly macros to embed in the format strings such as printf("blah %" FORMAT_FOR_FOO " rest of the string", a_foo);...Julio M. Merino Vidalhttp://www.blogger.com/profile/08233346614736256024noreply@blogger.comtag:blogger.com,1999:blog-17885055.post-23113906709374734162009-03-03T07:30:00.000+01:002009-03-03T07:30:00.000+01:00>this is C++, so you should be using iostreamsthis...>this is C++, so you should be using iostreams<BR/><BR/>this is joke, yes?<BR/><BR/>iostream is very not efficient in compare to printf,<BR/>but even if don't care how fast is your program or output doesn't put big value to all time there is problem of internalization.<BR/><BR/>cout << "My name is " << name << endl;<BR/><BR/>in different languages order of words is different, so you have to change all such code if you want add support of another language.<BR/><BR/><BR/>in compare <BR/>printf(i18n("My name is %s\n"), name);<BR/><BR/>you need change in one place in i18n function.<BR/><BR/>yeah, and about type safety,<BR/><BR/>gcc warn about types and format string mismatch, if you use another compiler you can use lint or something similar.Anonymousnoreply@blogger.com