Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!ut-sally!im4u!rutgers!ames!lll-tis!ptsfa!hoptoad!academ!uhnix1!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.lang.c
Subject: Re: Pet peeve #1473
Message-ID: <650@sugar.UUCP>
Date: Sat, 5-Sep-87 14:59:50 EDT
Article-I.D.: sugar.650
Posted: Sat Sep  5 14:59:50 1987
Date-Received: Wed, 9-Sep-87 05:41:39 EDT
References: <9001@brl-adm.ARPA> <526@clsib21.UUCP> <588@sugar.UUCP> <4319@teddy.UUCP>
Organization: Sugar Land UNIX - Houston, TX
Lines: 21

In article <4319@teddy.UUCP>, jpn@teddy.UUCP (John P. Nelson) writes:
> >Well, some PC compilers have cpp as a builtin. In fact I'd say most
> >PC compilers do this. There's no way to get the cpp output.
> 
> Well, I dont know about *most* PC compilers, but both Microsoft C
> and Turbo C have ways to get preprocessed output.  TurboC provides
> a seperate preprocessor program, even though the regular compiler
> has the preprocesser built-in!

Well, Microsoft 'C' (as of Version 3) is actually a port of their Xenix
compiler, so it's sort of the exception that proves the rule. Turbo 'C'
is beginning to look like an exception to all the rules. However, those
of us with Lattice, Aztec, or Microsoft pre-version-3 are still up the
creek. I don't know about Mix, de Smet, ECO-C, or Mark Williams... but I
would be surprised to learn they're any different. In the Mac, most 'C'
compilers are monolithic for speed. On the Amiga, both Lattice and Aztec
faithfully acrry on the bugs in their PC versions. Aztec even has memory
models (on a 68000!).
-- 
-- Peter da Silva `-_-' ...!seismo!soma!uhnix1!sugar!peter
--                 'U`  <-- Public domain wolf.