Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!aurora!labrea!jade!eris!mwm
From: mwm@eris.BERKELEY.EDU (Mike (My watch has windows) Meyer)
Newsgroups: comp.sys.amiga
Subject: 16 bit Lattices? (Was: AllocMem() with 16-bit Manx)
Message-ID: <5136@jade.BERKELEY.EDU>
Date: Fri, 18-Sep-87 07:50:56 EDT
Article-I.D.: jade.5136
Posted: Fri Sep 18 07:50:56 1987
Date-Received: Sun, 20-Sep-87 00:38:15 EDT
References: <8709141841.AA06918@cory.Berkeley.EDU> <1584@gryphon.CTS.COM>
Sender: usenet@jade.BERKELEY.EDU
Reply-To: mwm@eris.BERKELEY.EDU (Mike (My watch has windows) Meyer)
Organization: Missionaria Phonibalonica
Lines: 23

In article <1584@gryphon.CTS.COM> jdow@gryphon.CTS.COM (Joanne Dow) writes:
<>	I would suggest Aztec-C mainly because it will compile int's as either
<>16 bits or 32 bits (Most Atari compilers use 16 bit ints), and you don't want
<>to have to worry about a program compilable under BOTH 16 and 32 bit ints.
<>
<So does Lattice these days. 3.10 handles 16 bit or 32 bit integers nicely.

3.10 will make "int"'s 16 bit objects? How do I convince it to do
that? It isn't in the docs!

Of course, short's are 16 bits, and you can make it generate
pc-relative code and register-relative data ("small" code & data), but
that isn't the same thing. You still get stuck pushing 32 bit objects
on the stack for everything, and evaluating expressions in 32-bit
objects.

	<mike

--
All around my hat, I will wear the green willow.		Mike Meyer
And all around my hat, for a twelve-month and a day.	mwm@berkeley.edu
And if anyone should ask me, the reason why I'm wearing it,	ucbvax!mwm
It's all for my true love, who's far far away.		mwm@ucbjade.BITNET