Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!tandem!zorch!amiga0!mykes From: mykes@amiga0.SF-Bay.ORG (Mike Schwartz) Newsgroups: comp.sys.amiga.programmer Subject: SAS C 5.10A has problems Message-ID: Date: 20 Jun 91 04:37:18 GMT Organization: Amiga makes it possible Lines: 38 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 #1: BLINK complains about "extern struct Custom custom;" It prints a cryptic error message like "offset too far from A4". I was able to fix it by doing "extern struct Custom far custom;" which may or may not be preferable anyway (I say it is debatable :) Many of the GfxMacros.h macros rely on this custom variable. 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. Problem #3: When compiling various sources, I get "Invalid section type in memory option" error message. I could find no documentation for this error message... Unhappily working in C, Mykes :):):) (hope that's enough smileys) -- **************************************************** * I want games that look like Shadow of the Beast * * but play like Leisure Suit Larry. * ****************************************************