Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site l5.uucp
Path: utzoo!watmath!clyde!burl!ulysses!gamma!epsilon!zeta!sabre!petrus!bellcore!decvax!decwrl!sun!l5!gnu
From: gnu@l5.uucp (John Gilmore)
Newsgroups: net.micro.mac
Subject: Re: Macintosh Revealed, possible C header files
Message-ID: <161@l5.uucp>
Date: Fri, 27-Sep-85 16:52:31 EDT
Article-I.D.: l5.161
Posted: Fri Sep 27 16:52:31 1985
Date-Received: Wed, 2-Oct-85 00:37:00 EDT
References: <3167@nsc.UUCP> <1516@cbosgd.UUCP>
Organization: Ell-Five [Consultants], San Francisco
Lines: 21
Summary: How about *portable* header files for *all* Mac C's?

In article <1516@cbosgd.UUCP>, db@cbosgd.UUCP (J. Muir) writes:
> I purchased MR Vol II at MACWORLD Expo and got a chance to talk to
> Steve C. as he was autographing my copy (eat your hearts out!).
> On behalf of all C programmers out there, I submitted a plea for an
> addendum volume containing the interface descriptions and some examples
> in C.  On behalf of myself, I answered the "which dialect" question
> with "Aztec C" (sorry Mac C and Megamax owners).

It's hard to believe that any three products that call themselves
"C" (and get away with it) and compile for the same machine can't be
made to compile the same source and get it to run correctly.  Unless
I (or they) are totally off the wall, a set of include files or manuals
for the Mac interfaces should be pretty easy to write portably.

(Of course there will be a few things that need #ifdef-ing, like in
any modern-day portable C program...unfortunate but true.)

If the problem is that each C vendor provided Mac interfaces but named
them all differently, a set of public domain #include files that translated
one set of names to the other would be easy to produce, making it possible
to port something that had been written for a different interface library.