|Linkers & Loaders, books & article references sought firstname.lastname@example.org (1991-01-23)|
|Re: Linkers & Loaders, books & article references sought mwette@mr-ed.Jpl.Nasa.Gov (1991-01-24)|
|Re: Linkers & Loaders, books & article references sought email@example.com (1991-01-24)|
|Re: Linkers & Loaders, books & article references sought firstname.lastname@example.org.Virginia.EDU (1991-01-25)|
|Re: Linkers & Loaders, books & article references sought email@example.com (1991-01-25)|
|Re: Linkers & Loaders, books & article references sought Christian.Collberg@DNA.LTH.Se (Christian S. Collberg) (1991-01-27)|
|From:||firstname.lastname@example.org (Douglas W. Jones)|
|Date:||25 Jan 91 15:01:31 GMT|
In article <email@example.com> Neil Murray writes:
> On recent perusal of my bookshelf I noticed a goodly number of
> books on compiler theory but very little on linkers & loaders.
Perhaps this article would help:
D. W. Jones. "Assembly Language as Object Code." Software Practice and
Experience, Vol 13, No. 8, pages 715-725.
In this paper, I point out that a decent assembler (with macro and
conditional features, as well as a source inclusion directive) can
do everything we usually associate with linkage editors from the
FORTRAN generation (with the exception of automatic overlay management).
The particular assembler described in this paper is available from me
Return to the
Search the comp.compilers archives again.