Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!decwrl!pyramid!amiga!jimm
From: jimm@amiga.UUCP
Newsgroups: net.micro.amiga
Subject: Re: Question about Alink
Message-ID: <1201@amiga.amiga.UUCP>
Date: Thu, 22-May-86 00:51:33 EDT
Article-I.D.: amiga.1201
Posted: Thu May 22 00:51:33 1986
Date-Received: Fri, 23-May-86 02:13:23 EDT
References: <928@h-sc2.UUCP> <263@cbmvax.cbmvax.cbm.UUCP>
Reply-To: jimm@homer.UUCP (Jim Mackraz)
Distribution: na
Organization: Commodore-Amiga Inc., 983 University Ave #D, Los Gatos CA 95030
Lines: 18

In article <263@cbmvax.cbmvax.cbm.UUCP> daveh@cbmvax.UUCP (Dave Haynie) writes:
>
>First of all, the programs in C: were compiled under Greenhill's C, not
>Lattice.  The reason Lattice programs get so big is that the Lattice object
>modules in the Lattice linker library contain too many functions each.  

>ALINK includes ALL of the code in any object module referenced, even if
>only one function from within those objects is used.

Yes, this is how alink works.  On the suns we use Greenhills, alright,
but we use the same alink  and the same amiga.lib (more or less) that one
finds on a "lattice" development disk.

The extra code comes from the lattice lib and it's start-up module.
It has appeared in this newsgroup: using the different levels of 
lattice i/o functions brings in different amounts of code from lc.lib.
The startup code even knows how to get a window open for standard output,
when a program is opened from the workbench.