Xref: utzoo comp.lang.c:6478 comp.sys.m68k:671
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!mtune!codas!ateng!chip
From: chip@ateng.UUCP (Chip Salzenberg)
Newsgroups: comp.lang.c,comp.sys.m68k
Subject: Re: C machine
Message-ID: <147@ateng.UUCP>
Date: 8 Jan 88 20:52:23 GMT
References: <7535@alice.UUCP> <8226@steinmetz.steinmetz.UUCP> <461@auvax.UUCP> <9961@mimsy.UUCP> <166@teletron.UUCP> <6936@brl-smoke.ARPA>
Reply-To: chip@ateng.UUCP (Chip Salzenberg)
Organization: A T Engineering, Tampa, FL
Lines: 17

Andrew Scott asks:
>Why would a compiler vendor for the 68000 choose a 32 bit size for an int?

To which Doug Gwyn replies:
>To make it easier to port sloppily-written VAX code.

Yes -- but not all compiler writers have buckled under the great mass of
"AllTheWorldsAVax" programs.  The most popular C compilers available for
the Commodore Amiga (Manx and Lattice) have different sizes for "int"!
One is 16 bits (int==short) and the other is 32 bits (int==long).

I prefer 16 bits myself, but that's a religious issue, and far be it from
me to start an argument.  :-)
-- 
Chip Salzenberg                 UUCP: "{codas,uunet}!ateng!chip"
A T Engineering                 My employer's opinions are a trade secret.
    "Anything that works is better than anything that doesn't."  -- me