Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!bellcore!ulysses!allegra!mit-eddie!think!harvard!caip!cbmvax!daveh
From: daveh@cbmvax.cbm.UUCP (Dave Haynie)
Newsgroups: net.micro.amiga
Subject: Re: Question about Alink
Message-ID: <263@cbmvax.cbmvax.cbm.UUCP>
Date: Tue, 20-May-86 14:12:07 EDT
Article-I.D.: cbmvax.263
Posted: Tue May 20 14:12:07 1986
Date-Received: Thu, 22-May-86 02:02:19 EDT
References: <928@h-sc2.UUCP>
Reply-To: daveh@cbmvax.UUCP (Dave Haynie)
Distribution: na
Organization: Commodore Technology, West Chester, PA
Lines: 25

In article <928@h-sc2.UUCP> wen_2@h-sc2.UUCP writes:
>*** I refuse to believe in the lin
>
>Is it possible for those of us outside of West Chester and Los Gatos to use
>Alink to produce short executables?  For example, is it possible to link a
>"hello, world" to a less-than-10K executable, and how is this done?  I know
>it IS done, (look in c: for examples) but can I do it, too?

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.  If Lattice were to
distribute a library in which each function (or very small group of
closely-related functions) were in a separate object module, your code
would shrink quite a bit.  Why this isn't done, who knows?  You'd think
that Lattice is feeling some of the heat from Aztec's C, which doesn't have
this problem.

-- 

Dave Haynie    {caip,inhp4,allegra,seismo}!cbmvax!daveh
               "There, beyond the bounds of your weak imagination
                Lie the noble towers of my city, bright and gold"
								-Genesis