Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!hal!ncoast!davewt
From: davewt@NCoast.ORG (David Wright)
Newsgroups: comp.sys.amiga
Subject: Re: __chip keyword is evil
Summary: no it's not
Keywords: __chip, evil
Message-ID: <1989Dec19.200224.29753@NCoast.ORG>
Date: 19 Dec 89 20:02:24 GMT
References: <10415@etana.tut.fi> <9532@microsoft.UUCP> <411@enuxha.eas.asu.edu> <6@microsoft.UUCP>
Reply-To: davewt@ncoast.ORG (David Wright)
Organization: North Coast Public Access UN*X, Cleveland, OH
Lines: 12


	There is nothing wrong with using keywords like __chip or
__fast in a C program. True, they are not portable, but SO WHAT?? No other
system NEEDS them. They fill a need on the Amiga, and there is no way
to make them portable. It is a requirement of the Amiga to be able to
specify WHICH type of memory a certain segment belongs in. You can't use
ANY of the ANSI definitions (or the Microcrud either), as these are also
implemented on the Amiga and are used for different reasons.
	There is absolutely NOTHING wrong with putting in non-portable
keywords or definitions in ANY C program, when it is done for these
reasons, and when it is so easy to remove when transfering code to
another machine.