When I find my code in tons of trouble, Friends and colleagues come to me, Speaking words of wisdom: Write in C. As the deadline fast approaches, And bugs are all that I can see, Somewhere, someone whispers: Write in C. Write in C, write in C, Write in C, oh, write in C. LOGO's dead and buried, Write in C. I used to write a lot of FORTRAN, For science it worked flawlessly. Try using it for graphics! Write in C. If you've just spent nearly 30 hours, Debugging some assembly, Soon you will be glad to Write in C. Write in C, Write in C, Write in C, yeah, Write in C. BASIC's not the answer. Write in C. Write in C, Write in C Write in C, oh, Write in C. Pascal won't quite cut it. Write in C.
See also:
Lars H, 2011-07-25: Sometimes it seems to me that the phrase "write in C", especially among Tclers, might have a spin that is quite different from what this song gives it; rather than advocating C over such oldies as Pascal, FORTRAN, and the like, it advocates plain C over its "successors" such as C++, C#, and Java. A common sentiment seems to be that "Yes, language C' has feature X, but you can easily do that in plain C too with the help of a few Tcl Portable Runtime Library functions (and that actually makes your code more reliable)." Could anyone confirm/correct/elaborate this?AMG: At work someone asked me what my favorite object oriented programming language was. I answered, "C". He said it warmed his heart to hear that.
