Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!sri-unix!sri-spam!mordor!lll-tis!ames!ucbcad!zen!dorothy.Berkeley.EDU!c9c-eh
From: c9c-eh@dorothy.Berkeley.EDU (Warner Young (WHY))
Newsgroups: comp.sys.atari.st
Subject: Re: writing assembler
Message-ID: <4225@zen.berkeley.edu>
Date: Fri, 9-Oct-87 14:34:11 EDT
Article-I.D.: zen.4225
Posted: Fri Oct  9 14:34:11 1987
Date-Received: Sun, 11-Oct-87 17:03:13 EDT
References: <164100006@uiucdcsb>
Sender: news@zen.berkeley.edu
Reply-To: c9c-eh@dorothy.Berkeley.EDU.UUCP (Warner Young (WHY))
Organization: University of California, Berkeley
Lines: 19

In article <164100006@uiucdcsb> price@uiucdcsb.cs.uiuc.edu writes:
>
>Can anyone mail me a description of any of the more common .o file
>formats, and/or a description of the executable file format.  I have
>been able to decipher some things on my own using a PD disassembler
>and a hex dump program, but this tends to be painful...
>
>Bob Price

	I, too, would like to receive a description of the executable
file format.  Also, I would like to know what format the Alycon assembler
uses to generate its own .o files.  How are the external routines
referenced?  How does the Alycon linker work on these?

					MEGA-thanks,

					Warner Young

Disclaimer:  What statements?