Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!bbn.com!nic!chaos.cs.brandeis.edu!chaos!phils From: phils@chaos.cs.brandeis.edu (Phil Shapiro) Newsgroups: comp.sys.mac.programmer Subject: Re: LSC and MPW C ansi? Message-ID: Date: 11 Sep 90 15:44:31 GMT References: <1990Sep6.221626.16555@sics.se> <1990Sep7.134415.15193@eng.umd.edu> Sender: @chaos.cs.brandeis.edu Organization: Symantec Corp. Lines: 22 In-Reply-To: russotto@eng.umd.edu's message of 7 Sep 90 13:44:15 GMT In article <1990Sep7.134415.15193@eng.umd.edu> russotto@eng.umd.edu (Matthew T. Russotto) writes: In article <1990Sep6.221626.16555@sics.se> ollef@sics.se (Olle Furberg) writes: >Could someone tell me which versions (if any) of LSC and MPW C are ANSI-comp.? > > /Olle MPW versions 3.0 and up. None of the Lightspeed C's are ansi-compliant, and the differences are enough to drive you crazy. (sizeof doesn't return size_t, for instance) Unless I'm mistaken... MPW 3.2 (and lower) aren't fully ANSI compliant, the problem being that MPW supports extensions that can't be disabled (such as using '.' in a macro name). According to Michael Kahl, the Principal Architect of Think C, the next major release of Think C will be fully ANSI compliant. -phil shapiro, symantec tech support -- Phil Shapiro phils@chaos.cs.brandeis.edu