Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!asuvax!enuxha!martin
From: martin@enuxha.eas.asu.edu (Ross D. Martin)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice bugs still?
Summary: __chip is great.  Leave it alone!
Message-ID: <411@enuxha.eas.asu.edu>
Date: 15 Dec 89 04:24:48 GMT
References: <10415@etana.tut.fi> <9532@microsoft.UUCP>
Organization: Arizona State Univ, Tempe
Lines: 27

In article <9532@microsoft.UUCP>, w-edwinh@microsoft.UUCP (Edwin Hoogerbeets) writes:
> 	# pragma token-sequence[opt]
>
> causes the processor to perform an implementation-dependent action. An
> unrecognized pragma is ignored.
> 
> Why __chip? We've got the PORTABLE mechanism already. Why not use it?
> Was there some good technical reason? (__chip must go. This is not 
> negotiable. ;-)

Yes it is.  :-)

> 
> The idea behind __chip is good, though. It would be really useful to
> have as a pragma. 
> 
> Edwin
> Reading legalese mush can turn your brain to guacamole. - RKMs A&I

I don't see what you have against __chip.  It is portable.  Just #define
it to something harmless to do a port.  I believe you can #define something
to a null string, can't you?  If not, there are several do-little modifiers
out there that should work ok.  Perhaps #define __chip static?
Pragmas involve more typing to get less clear, clean code.  Not a good idea
in my book.

		Ross Martin