CompuServe Messages

PrettyPrint.c

    11-Jan-88 12:46:25
Sb: #102791-PrettyPrint.c
Fm: Richard Rae/SYSOP 76703,4253
To: John Draper 76703,4322
Come on, Larry, you're still attributing things to the LANGUAGE which are the fault of the programmers: "Shouldn't you… for the sake of… C PROGRAMMERS… write the code… with arcane indents, blocks of punctuation and simple character variables unspoiled by verbose traces of other languages?" Sheesh, gimme a break. Scr*w what K&R might want. Write CLEAN, READABLE, MAINTAINABLE CODE! 8) "Typos are the bane of programmers… C is helped by afterthoughts." Har. In lots of cases C is better off than other languages. Try typing INRQO when you meant INRQ0 in FORTRAN or BASIC or yes, even assembly language and see what happens. The compiler/interpreter/assembler won't complain, but neither will your code run. C will inform you that you have used an undeclared variable. I have seen some TERRIBLE code written in FORTRAN and BASIC, but I've seen some pretty good stuff too. Nearly everyone hates COBOL, but a lot of that is from the shortcuts: I've seen COBOL from crackerjack programmers that is really well done and almost looks structured. Even assembly language can be used or abused. C is no exception, and I doubt Pascal, Modula, or Ada are either. Let's be fair to ALL the languages. It's a poor workman who blames his tools. If programmer "x" writes unreadable code in language "y", which one is REALLY at fault? Rick