Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!mcsun!cernvax!chx400!bernina!wild
From: wild@nessie.cs.id.ethz.ch (Markus Wild)
Newsgroups: comp.sys.amiga.programmer
Subject: Re:  New Eiffel-like OOP language
Message-ID: <1991Jun29.232046.6932@bernina.ethz.ch>
Date: 29 Jun 91 23:20:46 GMT
References: <1991Jun17.161534.323@nntp-server.caltech.edu> <15547@exodus.Eng.Sun.COM> <ben.3470@epmooch.UUCP>
Sender: news@bernina.ethz.ch (USENET News System)
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
Lines: 22
Nntp-Posting-Host: nessie

In article <ben.3470@epmooch.UUCP> ben@epmooch.UUCP (Rev. Ben A. Mesander) writes:
[.....]
>file. The problems I was having with compiling GNU chess went away in
>the latest release, but some other people have reported problems with
>f2c output still causing  SAS/C to generate incorrect branches in the
>presence of very large functions.

So why don't you just use gcc for those huge beasts? Gcc doesn't have 
such 16bit problems, it doesn't have problems with huge macros, so I
can really see no reason why not to use it for such programs as gnu-chess,
that won't use any amiga-special features (like __chip) or on the
output of a fortran-converter. Depending on your personal preferences,
you can run the output thru converters to generate either Manx object
files or hunk format object files (for you BLINK users..), or you can
use gnu-ld to directly generate load-files, completely avoiding the use
of a certain monster called "official" linker;-))
For those without gcc, it can be obtained (the converters and gnu-ld too)
from nic.funet.fi.

-Markus
-- 
Markus M. Wild    - mwild@iiic.ethz.ch  |  wild@nessie.cs.id.ethz.ch