Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!rutgers!labrea!jade!ucbvax!CORY.BERKELEY.EDU!dillon From: dillon@CORY.BERKELEY.EDU (Matt Dillon) Newsgroups: comp.sys.amiga Subject: Re: AllocMem() with 16-bit Manx Message-ID: <8709141841.AA06918@cory.Berkeley.EDU> Date: Mon, 14-Sep-87 14:41:52 EDT Article-I.D.: cory.8709141841.AA06918 Posted: Mon Sep 14 14:41:52 1987 Date-Received: Tue, 15-Sep-87 06:36:05 EDT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 25 >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. The difficulty wasn't Aztec-C itself, but the fact that the originator was not familar with the problems that usually crop up when one is using 16 bit integers. >If YOU had to write a massive game program for the Amiga and later port >it to the Atari ST and Apple //gs (forget about the gs, that'll be in assembly) >what would you pick as a 'c' development system? And why? I would: (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. -Matt