Xref: utzoo comp.sys.amiga.programmer:4609 comp.sys.amiga.misc:4668 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!pa.dec.com!bacchus!mwm From: mwm@pa.dec.com (Mike (My Watch Has Windows) Meyer) Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.misc Subject: Re: New Eiffel-like OOP language Message-ID: Date: 17 Jun 91 14:39:25 GMT References: <1991Jun16.063222.1304@csis.dit.csiro.au> <1991Jun16.145750.14475@schaefer.math.wisc.edu> Sender: news@pa.dec.com (News) Organization: Missionaria Phonibalonica Lines: 41 In-Reply-To: mueller@schaefer.math.wisc.edu's message of 16 Jun 91 14:57:50 GMT In article <1991Jun16.145750.14475@schaefer.math.wisc.edu> mueller@schaefer.math.wisc.edu (Carl Mueller) writes: In article <1991Jun16.063222.1304@csis.dit.csiro.au> dave@csis.dit.csiro.au (David Campbell) writes: >G'day! > >I think we can give up hope of compiling anything serious with Lattice C, > Wait a second ... why do you say this? I have Lattice C (SAS/C) version 5.10 and haven't had any troubles compiling stuff. Well, if he only looks at GNU software, which is generally written as if memory were an infinite resource (among other problems), then I can see what would cause him to say that. I haven't had any real problems with it, and I _have_ compiled "serious" software with it. RCS (both of them) didn't create any serious problems. The byte code emulator for OAKLISP (a complete OO LISP System) works just fine, and I've got a disk ready to go to Fred Fish. The support library and REPL loop for Scheme->C (DEC's Scheme interpreter/compiler system) compiles with no problems, but I'm still chasing out the Unixisms. Having looked over the Sather source code (and rejecting it as a worthwhile thing to port), I don't think it would create any serious problems for the compiler. That Sather garbage collects the C stack in a rather ugly manner might cause problems. But that won't cause any more problems with SAS/C than it does with GNU. However, there are some good reasons for using GNU C for a Sather port.Mostly, Sather is liable to have been made to work with GNU C on Unix, so a lot of minor stuff will have been take care of. That you can't use GNU C on small machines isn't a real problem here - if your machine isn't big enough to run GNU C, then any non-trivial Sather application probably is probably going to have problems.