Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!bu.edu!snorkelwacker.mit.edu!ira.uka.de!fauern!forwiss.uni-passau.de!unipas!hessmann
From: hessmann@unipas.fmi.uni-passau.de (Georg Hessmann)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: SAS C 5.10A has problems
Message-ID: <1991Jun24.110845.19273@forwiss.uni-passau.de>
Date: 24 Jun 91 11:08:45 GMT
References: <mykes.3672@amiga0.SF-Bay.ORG>
Sender: usenet@forwiss.uni-passau.de (USENET News System)
Organization: University of Passau, Germany
Lines: 45
Nntp-Posting-Host: unipas.fmi.uni-passau.de

In article <mykes.3672@amiga0.SF-Bay.ORG> mykes@amiga0.SF-Bay.ORG (Mike Schwartz) writes:
>Not to start a new round of language wars, but I have been working
>with SAS 'C' for a few weeks (yes, I still write lots of assembler, too :)
>
>Anyway, I've found that SAS is full of bugs and problems, many of which I
>can find workarounds.  At this point, I would like to get (perhaps) some
>answers from anyone on the net who might have solutions.  E-Mail might
>be preferable, but if you think there is value to others in the solutions,
>please post.

[...]

>Problem #2:
>	When compiling some sources, I get CXERR: 99, which is NOT documented
>in the manual.  Nice messages, eh folks?  Real descriptive :)  The compiler
>does not complain about anything else in the source file.  This error comes up
>during the Optimizing phase.

I've got this message, too.
The reason was a varargs function.
If you use varargs functions with the 'va_list' type, try two things:
First, declare the funktion as __stdargs and second, declare the 'va_list'
variable as 'volatile'.

E.g.:
void __stdargs Message(char *fmt, ...)
{
  volatile va_list list:
...
}


[...]
>
>Unhappily working in C,
>Mykes
>
>:):):)
>
>(hope that's enough smileys)


	Georg.
-- 
  hessmann@unipas.fmi.uni-passau.de		hessmann@unipas.uucp