Linked by Eugenia Loli on Mon 10th Oct 2005 16:48 UTC, submitted by Shlomi Fish
General Development Shlomi Fish has written a new essay titled "When C is the Best? (Tool for the Job)". Its theme is giving several reasons (besides high speed and low memory consumption) why some code should still be written in C.
Permalink for comment 42717
To read all comments associated with this story, please click here.
RE[2]: C and portability
by the_trapper on Mon 10th Oct 2005 19:38 UTC in reply to "RE: C and portability"
the_trapper
Member since:
2005-07-07

Illusion ? It is the most portable language (of course, by portability we mean source code portability).

It's portable as long as your program only does portable things, like text processing and math.

However, C is a portability nightmare when it comes to things like networking, graphics, and several other things. Additionally, people talk about C like there's only one version of it. There are in fact several, the most popular of which are K&R, ANSI C 89, ANSI C 99, and GNU C. Yes, GNU C does add its own extensions, and yes programmers do use them. (It is possible to have vendor lock-in in open source, it just isn't as big of a problem when it happens.)

C is also unportable during the act of compiling and linking. There are several different C compilers that use different command line options. Commonly used C libraries can be placed in any number of locations and given any number of names on people's computers. That's why we have the mess that is the GNU autotools.

Reply Parent Score: 1