Path: utzoo!attcan!uunet!lll-winken!muslix!jac
From: jac@muslix.llnl.gov (James Crotinger)
Newsgroups: comp.sys.amiga.tech
Subject: Re: __chip is evil
Message-ID: <42761@lll-winken.LLNL.GOV>
Date: 31 Dec 89 07:05:04 GMT
References: <10415@etana.tut.fi> <9532@microsoft.UUCP> <1388@sas.UUCP> <10016@microsoft.UUCP>
Sender: usenet@lll-winken.LLNL.GOV
Reply-To: jac@muslix.UUCP (James Crotinger)
Organization: Lawrence Livermore National Laboratory/UC Davis
Lines: 19


  I guess I'll give up and add my two cents to the __chip vs. #pragma
argument. I'm in favor of __chip (and all of Lattice's other "pollution")
for the following reason: it localizes important information about the
variable. Putting all these into #pragma's in a pragma.h file is a software
engineering nightmare! Especially the _d0 type of stuff, where if you 
try to call that function from another file, and haven't properly prototyped
the function (by forgeting to type all the #pragmas), then you'll be wrong. 
Sure, you can localize the #pragmas, but I think:

#pragma chip foo
long foo[100];

#pragma chip bar
long bar[30];

is much uglier than using __chip.

  Jim