Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!mcnc!ece-csc!ncrcae!ncr-sd!crash!gryphon!jdow
From: jdow@gryphon.CTS.COM (Joanne Dow)
Newsgroups: comp.sys.amiga
Subject: Re: request: object file format
Message-ID: <1193@gryphon.CTS.COM>
Date: Wed, 12-Aug-87 03:09:47 EDT
Article-I.D.: gryphon.1193
Posted: Wed Aug 12 03:09:47 1987
Date-Received: Fri, 14-Aug-87 06:20:18 EDT
References: <8708080430.AA18861@cogsci.berkeley.edu>
Reply-To: jdow@gryphon.CTS.COM (Joanne Dow)
Organization: Trailing Edge Technology, Redondo Beach, CA
Lines: 20
Keywords: object format, request, alink

In article <8708080430.AA18861@cogsci.berkeley.edu> bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt) writes:
>In article <@altura> krueger@srcsip.UUCP (Jonathan W Krueger) writes:
>
>> I am about to embark on some experimental language development and need to
>> know the format for object files used as input to the Amiga linker(s) Alink
>> (and Blink?).  Any direct or indirect pointers to a specification would be
>> most welcome.
>
>The format is described in Commodore's "AmigaDOS Technical Reference Manual".  I
>suspect, but have not verified, that this information was carried over to 
>Bantam Book's "The AmigaDOS Manual, 2nd edition" (Bantam Books, New York, NY).
>
>The "AmigaDOS Manual" should be available at Amiga dealers and/or Waldenbooks.

There are additional formet elements supported by the blink linker. These are
targeted to small model code development. I suggest finding a copy of blink6.7
for documentation on these features. (It appears blink7.0, which will be a
Lattice property, will support even more.)
<@_@>
	Remember that a bird in the hand . . . er often leaves a sticky deposit.