Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!rpi!netserv2!deven From: deven@rpi.edu (Deven T. Corzine) Newsgroups: comp.sys.amiga.tech Subject: Re: __chip is evil Message-ID: Date: 4 Jan 90 14:47:23 GMT References: <85006@linus.UUCP> Organization: Rensselaer Polytechnic Institute, Troy, NY Lines: 30 In-Reply-To: duncant@mbunix.mitre.org's message of 28 Dec 89 00:02:37 GMT On 28 Dec 89 00:02:37 GMT, duncant@mbunix.mitre.org (Thomson) said: Thomson> Of course there will always be those who don't care about Thomson> whether they are writing in "standard" C. As long as their Thomson> code compiles with their compiler they are happy. This is OK Thomson> for code which will never be distrubuted, but if you intend Thomson> to pass your code around PLEASE make an effort to conform to Thomson> the standard. Um, excuse me, but what point is there in using "standard" C when there's no way the code will be portable? Chip memory is specific to the Amiga architecture; anything which must be in chip memory won't run on another machine anyhow. At least __chip is more logical than adding another bizarre #pragma syntax. Any special graphics and sound programs you write for the Amiga certainly aren't going to run unmodified on a Unix box. If portability among Amiga compilers is a concern, then by all means, use AllocMem. But, if other Amiga compiler-writers were to follow Lattice's example and incorporate __chip, it wouldn't be a problem. Certainly a far better solution than all those old "fixhunk" programs to run on binaries... Deven -- Deven T. Corzine Internet: deven@rpi.edu, shadow@pawl.rpi.edu Snail: 2151 12th St. Apt. 4, Troy, NY 12180 Phone: (518) 274-0327 Bitnet: deven@rpitsmts, userfxb6@rpitsmts UUCP: uunet!rpi!deven Simple things should be simple and complex things should be possible.