Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!ihlpf!nevin1 From: nevin1@ihlpf.ATT.COM (00704A-Liber) Newsgroups: comp.lang.c Subject: Re: parens honored Keywords: ANSI C standard Message-ID: <3335@ihlpf.ATT.COM> Date: 12 Jan 88 01:04:50 GMT References: <6829@brl-smoke.ARPA> <2845@zeus.TEK.COM> <6860@brl-smoke.ARPA> <7009@brl-smoke.ARPA> <7563@elsie.UUCP> Reply-To: nevin1@ihlpf.UUCP (00704A-Liber,N.) Organization: AT&T Bell Laboratories - Naperville, Illinois Lines: 15 In article <7563@elsie.UUCP> ado@elsie.UUCP writes: >To me, the real problem with honoring parentheses is simple: existing >implementations of C don't. This means that when an ANSI C program that >"needs" such honoring gets ported back to an existing implementation, >things will break quietly and mysteriously. Although I am also against honoring parens I can't use your argument. ANYTHING using a feature which ANSI C has and existing implementations of C don't have CANNOT be ported back to existing implementations (although I agree that it is bad to change the language in such a way that code will break 'quietly'). -- _ __ NEVIN J. LIBER ..!ihnp4!ihlpf!nevin1 (312) 510-6194 ' ) ) "The secret compartment of my ring I fill / / _ , __o ____ with an Underdog super-energy pill." / (_