gnu (03/25/83)
Sorry, Dave, but MY C pet peeve is people who write the superfluous parentheses in return statements just because PL/1 did it that way. I like being able to say return 0; and it returns zero. And there are plenty of places where leaving out a semicolon will break your program invisibly; that's not good reason to change the language. John Gilmore, Sun Microsystems
idallen (03/28/83)
There are plenty of places where leaving out a semicolon will break your program invisibly; that's not good reason to change the language. -- John Gilmore, Sun Microsystems If changing return/sizeof so that parentheses are required removes even one of these invisible places, isn't that a step in the right direction? -IAN! (Ian! D. Allen) idallen@watmath.uucp University of Waterloo decvax!watmath!idallen
gnu (03/28/83)
Ian Allen is right. Let's change everything in the language so it needs parens before the semicolon. The extra redundancy will make typing errors so much more detectable. And the lisp hackers will love us. John Gilmore, Sun Microsystems
idallen (03/29/83)
Ian Allen is right. Let's change everything in the language so it needs parens before the semicolon. The extra redundancy will make typing errors so much more detectable. And the lisp hackers will love us. -- John Gilmore, Sun Microsystems I like redundancy. However, I think your suggestion is too extreme. -IAN! (Ian! D. Allen) idallen@watmath.uucp University of Waterloo decvax!watmath!idallen