Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!uwvax!oddjob!mimsy!chris From: chris@mimsy.UUCP (Chris Torek) Newsgroups: comp.lang.c Subject: Re: Annoyingly necessary spaces Message-ID: <12380@mimsy.UUCP> Date: 8 Jul 88 22:03:04 GMT References: <326@marob.MASA.COM> <2550075@hpisod2.HP.COM> <8227@brl-smoke.ARPA> Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742 Lines: 17 >In article <11812@agate.BERKELEY.EDU> weemba@garnet.berkeley.edu (Obnoxious Math Grad Student) asks whether `=op' operators are >>just a cloying Berkeleyism? In article <8227@brl-smoke.ARPA> gwyn@brl-smoke.ARPA (Doug Gwyn ) writes: >Yes. AT&T C compilers stopped supporting the =op form years ago. 4BSD stopped (a) year ago. They are gone in 4.3BSD-tahoe. Those programs that used them (Berkeley Pascal, struct) have been fixed. Old-fashioned initialisations are gone too. No more erroneous recovery (and corresponding error cascade) from int f(x) imt x; { ... -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163) Domain: chris@mimsy.umd.edu Path: uunet!mimsy!chris