Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!maytag!aries5!giguere
From: giguere@aries5.uucp (Eric Giguere)
Newsgroups: comp.sys.amiga.tech
Subject: Re: __chip is evil
Message-ID: <1243@maytag.waterloo.edu>
Date: 9 Jan 90 15:02:53 GMT
References: <85006@linus.UUCP> <4839@sugar.hackercorp.com> <86113@linus.UUCP>
Sender: daemon@maytag.waterloo.edu
Reply-To: giguere@aries5.UUCP (Eric Giguere)
Organization: Computer Systems Group, University of Waterloo
Lines: 21

In article <86113@linus.UUCP> duncant@mbunix.mitre.org (Thomson) writes:
>Again, I think that you guys are missing the point.  It seems to me that the
>ANSI committee provided #pragma  exactly for handling non-standard things,
>such as "__chip", which can't otherwise be done in the language.

I really don't know what the fuss is about.  It seems to me that "__chip"
is a good solution for a unique Amiga feature... after all, the MS-DOS
world has its "near", "far" and "cdecl" keywords.  I can't recall a passage
in the ANSI standard that specifically forbids implementation-specific
language extensions.  Personally I think a #pragma would be quite ugly and
confusing.  As for portability... well, as other people have pointed out,
it's unlikely that an Amiga program that uses the "__chip" keyword will be
portable anyhow....

I'd rather we discussed other matters, like Intuition under 1.4.... I
hope it will have higher level support functions....

Eric Giguere                                  268 Phillip St #CL-46
C'est un nom francais, bien sur               Waterloo, Ontario  N2L 6G9
Bitnet  : GIGUERE at WATCSG                   (519) 746-6565
Internet: giguere@aries5.UWaterloo.ca         "Nothing but urges from HELL!!"