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 42736
To read all comments associated with this story, please click here.
RE: Re: More Blah
by stew on Mon 10th Oct 2005 20:00 UTC in reply to "Re: More Blah"
stew
Member since:
2005-07-06

Endiness isn't that big of a problem. You have what: two possibilities?

And why on earth would I want to use a language that lets the programmer deal with it instead of doing it itself? I can't think of any situation where as a programmer you would want to have the endianess differences exposed to your programs (not even in drivers). Just make everything be big endian in source code level and let the compiler figure out how put that in machine language.

Also, null terminated byte arrays are a library convention. It's not a language feature. If you want to manipulate unicode, use the proper library.

So, no portable strings in C? It's only portable when I rely on the standard C library, which uses null-terminated strings. When I have to rely on other libraries, I lose the (supposed) portability.

Reply Parent Score: 1