Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

printf() considered garbage

Name: Anonymous 2013-06-26 6:47

Why not just use puts()? Is formatting your own strings properly really so hard? Maybe if you went to a school with a name that ended in `.com'. If that's the case, enjoy your security holes when you fuck up and put an %n somewhere or do something stupid like printf(str) and loosing buffer overflows all over the place. Not only that, but it's inefficient and bloated. I am sick and tired of seeing new programmers wasting CPU time and memory to run this huge, buggy function.

In general, it's never a bad idea to use something simpler if available.

Name: Anonymous 2013-06-26 7:39

>>2
Not to mention format strings are better for localisation. (They still suck though. The Right Thing would be the ability to patch entire functions at run-time, seamlessly (i.e. without “dynamic” library nonsense). It would also help with different calendars, etc. as well as allow the extension of programs at run-time.)

Name: 4 2013-06-26 7:47

(continued, explaining why “format strings are better for localisation”)

Format strings are functions written in domain-specific languages. In effect, systems such as GNU gettext are run-time function loaders.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List