Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!ames!nrl-cmf!cmcl2!brl-adm!brl-smoke!gwyn From: gwyn@brl-smoke.ARPA (Doug Gwyn ) Newsgroups: comp.lang.c Subject: Re: Annoyingly necessary spaces Message-ID: <8227@brl-smoke.ARPA> Date: 8 Jul 88 17:51:44 GMT References: <326@marob.MASA.COM> <2550075@hpisod2.HP.COM> <19782@watmath.waterloo.edu> <11812@agate.BERKELEY.EDU> Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB)) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 16 In article <11812@agate.BERKELEY.EDU> weemba@garnet.berkeley.edu (Obnoxious Math Grad Student) writes: >What I want to know is when the illegality of "i=++j" or the old-fashioned >syntax default of "s=*++t" and "m=--n" is going to go away. Is this just >a cloying Berkeleyism? Yes. AT&T C compilers stopped supporting the =op form years ago. >Will ANSI C make a difference, or is the weight of tons of old-fashioned >code going to decide matters? I believe there aren't many C compilers other than ones derived from the old version of PCC that Berkeley shipped that still support =op. ANSI C simply canonicalizes actual modern practice; I doubt that it will much affect the rate at which =op vanishes, except perhaps that as Standard conformance is required in future procurements more old code will end up finally getting fixed.