Newsgroups: comp.sys.amiga.programmer
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!unlinfo.unl.edu!fergvax!231b3678
From: 231b3678@fergvax.unl.edu (Phil Dietz)
Subject: Re: SAS C 5.10A has problems
Message-ID: <231b3678.677404397@fergvax>
Sender: news@unlinfo.unl.edu
Nntp-Posting-Host: fergvax.unl.edu
Organization: University of Nebraska - Lincoln
References: <mykes.3672@amiga0.SF-Bay.ORG>
Date: 20 Jun 91 07:53:17 GMT
Lines: 35

In <mykes.3672@amiga0.SF-Bay.ORG> mykes@amiga0.SF-Bay.ORG (Mike Schwartz) writes:

>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.

SAS has a problem with static character strings and or string formats.
For instance, if I do an extended printf like
 
printf("aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
       "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb"
       ...
       "zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz");
 
It will crap out.   If I say  *string= "aaaaa....a"
                                       "bbbbb....b"
                                       ...
                                       "zzzzz....z"
 
it will crap out too.   I think the compiler has limitations on stuff
like this.  They REALLY need to update there error messages (even if they
are internal).
 
SOLUTION:
 
Start commenting out code and re-compiling seeing if it will give an error or
not.  This is the long annoting way, but it works.


---                    
   FACT:  the Nebraska Cornhuskers                           Phil Dietz 
          signed a contract to lose the        231b3678@fergvax.unl.edu       
          big games!  Yes, it's true!                 Univ. of Nebraska
