Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!steinmetz!mizar!jesup
From: jesup@mizar.steinmetz (Randell Jesup)
Newsgroups: comp.sys.amiga
Subject: Re: AllocMem() with 16-bit Manx
Message-ID: <7361@steinmetz.steinmetz.UUCP>
Date: Tue, 15-Sep-87 01:00:41 EDT
Article-I.D.: steinmet.7361
Posted: Tue Sep 15 01:00:41 1987
Date-Received: Wed, 16-Sep-87 05:37:31 EDT
References: <8709141841.AA06918@cory.Berkeley.EDU>
Sender: root@steinmetz.steinmetz.UUCP
Reply-To: jesup@mizar.UUCP (Randell Jesup)
Organization: General Electric CRD, Schenectady, NY
Lines: 28

In article <8709141841.AA06918@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
>>Having just taken the plunge with a massive programming job on the Amiga, 
>>I find myself wondering which of the various 'C''s I should do the work
>>under.  I decided to post this message in this thread since it seems to
>>be pointing out some difficulties in using MANX....

>	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.

	Don't forget that Lattice 4.0 also handles 16-bit ints, AND it has
prototypes, which can save immeasurable problems like the originator of this
thread had (prototypes allow checking the types of all arguements).

>	(A) Get reference manuals on both computers
>	(B) Study them
>	(C) Write the game on one machine, organizing the machine dependant 
>	    stuff to make porting easier.

	I agree absolutely.  You might even want to write a small module
of routines for handling things that are different between the machines
BEFORE writing any of the other code (Line-Draws, file access, requesters,
open window, etc.)
--

	Randell Jesup  (Please use one of these paths for mail)
	mizar!jesup@steinmetz.UUCP (uunet!steinmetz!{mizar|crd}!jesup)
	jesup@ge-crd.ARPA