Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!spool.mu.edu!caen!uakari.primate.wisc.edu!unmvax!uokmax!servalan!epmooch!ben From: ben@epmooch.UUCP (Rev. Ben A. Mesander) Newsgroups: comp.sys.amiga.programmer Subject: Re: SAS gripes (was New Eiffel-like OOP language) Message-ID: Date: 28 Jun 91 12:22:21 GMT References: <1991Jun16.063222.1304@csis.dit.csiro.au> <1991Jun17.161534.323@nntp-server.caltech.edu> <15547@exodus.Eng.Sun.COM> <1991Jun21.164424.3364@nntp-server.caltech.edu> Organization: Elvis Presley Museum Of Obsolete Computing Hardware Lines: 26 In article Jay@deepthot.cary.nc.us (Jay Denebeim) writes: >In article <1991Jun21.164424.3364@nntp-server.caltech.edu> tll@nntp-server.caltech.edu (Tal Lewis Lancaster) writes: >> >>This is not true. Lattice/SAS and Manx compilers can not support function >>calls more than 32K away in the same object file!!! If you attempt it under >>SAS you will be visited by a CXERR: 29. I have confirmed these limitations >>with both companies! >> > >RTFM! Don't use the small memory model if you need modules bigger than >32K. I won't mention that its silly to have modules that big, I assume >you're just doing that as a test. Anyone working on serious code >makes the modules small so that they're easy to work with. Who pissed dioxin in your Post Toasties? RTFM indeed. With the large code model, SAS still sometimes has trouble with code more than 32K away in a single object file, especially if a single function is larger than 32K. I don't code this way, but the GNU people do in GNU chess, and it's pretty easy to generate such code with a tool like f2c given typical FORTRAN programming habits. -- | ben@epmooch.UUCP (Ben Mesander) |CNEWSMUSTDIECNEWSMUSTDIECNEWSM| | ben%servalan.UUCP@uokmax.ecn.uoknor.edu |USTDIECNEWSMUSTDIECNEWSMUSTDIE| | ...!chinet!servalan!epmooch!ben |CNEWSMUSTDIECNEWSMUSTDIECNEWSM|