Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!quanta.eng.ohio-state.edu!phao.eng.ohio-state.edu!dirks
From: dirks@phao.eng.ohio-state.edu (William R.Dirks)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice bugs still?
Summary: __chip is OK ANSI-wise
Keywords: __chip ANSI
Message-ID: <3756@quanta.eng.ohio-state.edu>
Date: 15 Dec 89 07:13:14 GMT
References: <10415@etana.tut.fi> <9532@microsoft.UUCP> <411@enuxha.eas.asu.edu>
Sender: news@quanta.eng.ohio-state.edu
Reply-To: dirks@phao.eng.ohio-state.edu (William R.Dirks)
Organization: The Ohio State University Dept of Electrical Engineering
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. ;-)

The following is quoted from the Lattice Amiga Compiler User's Guide
page G51 without permission.  (I hope they don't get mad at me. ;) )

  "The chip, far, huge, and near keywords are extensions to the ANSI
  standard.  The standard requires that each keyword extensions [sic]
  be preceded by a double underscore, such as __near.  The Lattice 
  compiler accepts the extended keywords in this form as well as in
  the more natural form without the double underscores."

I guess "__chip" is ANSI, but "chip" breaks the rules.

I am in no way affiliated with Lattice.
-=-
Bill Dirks					 ...a large iron bar
						suspended across a vast
dirks@kaa.eng.ohio-state.edu			 multitude of grapes...