Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!samsung!uunet!csun!news
From: swalton@solaria.csun.edu (Stephen Walton)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Which C-compiler can create true libraries?
Keywords: Amiga libraries.
Message-ID: <1991Jan11.003038.17471@csun.edu>
Date: 11 Jan 91 00:30:38 GMT
References: <1991Jan10.130040.13771@ida.liu.se>
Sender: news@csun.edu (News Administrator)
Reply-To: swalton@solaria.csun.edu (Stephen Walton)
Organization: Cal State Northridge
Lines: 25
In-Reply-To: micja@IDA.LiU.SE (Michael Jansson)

In article <1991Jan10.130040.13771@ida.liu.se>, micja@IDA (Michael
Jansson) writes:

>I'm currently using Manx 5.0a which I managed to force into creating a
>correct library.  Version 5.0d is a dead-end, even though it generates
>very nice code for ordinary programs.

I'm not sure what Michael means by "force."  It seems a well-kept
secret that the Manx 5.0a distribution has a complete example of a
resident library in the res_lib directory of disk 4.  All one needs to
do to produce one's own library is write the library functions,
#pragmas for them (easy) and list them in a table in the file called
libsup.c in that directory.

Manx 5.0d has, unfortunately, a couple of new bugs having to do with
library code generation.  To work around them:

1.  Add a dummy argument (I used int x) to the three routines in
libsup.c (myOpen, myClose, myExpunge).

2.  Do not optimize the actual library entry points, though
lower-level routines can be optimized fine.
-------------------------------
Stephen Walton, Dept. of Physics & Astronomy, Cal State Univ. Northridge
   I am srw@csun.edu no matter WHAT the stupid From: line says!