Replies

As Nancy Leveveson of MIT said, it is one of the most error-prone languages ever designed.

Spohen by someone who must have made a lot of mistakes. ;-D

I have used 'c' in everything from operating systems to applications. It is a wonderful language that "enables" everything one does. The more restrictive languages are reserved for those with less talent.

I have used 'c' in everything from operating systems to applications. It is a wonderful language that "enables" everything one does. The more restrictive languages are reserved for those with less talent.

Good lord! This thread looks like the Readers' Digest (very) condensed version of a thread on alt.sysadmin.recovery. "Very" condensed since it has't drifted into turn-indicator usage in GB versus in Oz. However, editor wars, OS wars (BSD is the ONE true code!), are all here though.

I had a boss back in the day who famously stated "C is a bad language because it lets you do things you shouldn't." Needless to say, the sysadmins quoted him frequently followed by huge guffaws of laughter.

I was never very good at C, though I could patch PINE installs, dink with Apache and so on. My handicap was learning FORTRAN first resulting in "pass by value" habits in a "pass by address" world.

Remember: There is COBOL code still in production today that is older than most of the Freepers on this thread.

“I have used ‘c’ in everything from operating systems to applications. It is a wonderful language that “enables” everything one does. The more restrictive languages are reserved for those with less talent.”

I’ll assume you’re kidding. If so, I’m kidding too:

All I can say is that I hope programmers like you stick with video games and stay away from anything safety critical.