home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.amiga.programmer:17756 comp.sys.amiga.misc:19011
- Path: sparky!uunet!gatech!pitt.edu!stern
- From: stern+@pitt.edu (Eric G Stern)
- Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.misc
- Subject: Re: Advice to SAS/C 5.10b users
- Message-ID: <1120@blue.cis.pitt.edu>
- Date: 23 Dec 92 19:18:18 GMT
- References: <BzM5Kw.CuD@unx.sas.com> <1992Dec22.233153.17212@oracle.us.oracle.com> <Bzpywu.85G@unx.sas.com>
- Sender: news+@pitt.edu
- Followup-To: comp.sys.amiga.programmer
- Organization: University of Pittsburgh
- Lines: 21
-
- In article <Bzpywu.85G@unx.sas.com> walker@twix.unx.sas.com (Doug Walker) writes:
-
- >Remember the original posting that started all this was by someone
- >who was advising others not to upgrade to V6 because of all the
- >bugs people were talking about on the net. This is partially
- >because only "bad news" is discussed here, but it is also partially
- >due to the fact that people tend to blame the compiler when their
- >code acts funny. [...]
- >=*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)460-7430 =
-
-
-
- Well, I'll say something good about SAS/C 6.1. I was trying to port
- the latest bison version 1.19 (the GNU project replacement for YACC)
- and had had weird problems with memory overwrites and crashes with
- 6.0. I didn't bother pursuing it at the time because I knew that 6.1
- was coming out imminently. When I upgraded to 6.1, all my problems
- went away and bison worked identically with its UNIX version on a
- silicon graphics.
-
- Eric Stern
-