Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!uunet!overload!dillon From: dillon@overload.Berkeley.CA.US (Matthew Dillon) Newsgroups: comp.sys.amiga.programmer Subject: Re: Object file format specs wanted. Message-ID: Date: 28 Feb 91 18:38:01 GMT References: <1991Feb27.211703.12787@csun.edu> Organization: Not an Organization Lines: 38 In article <1991Feb27.211703.12787@csun.edu> bcphyagi@csunb.csun.edu (Stephen Walton) writes: >In article ben@epmooch.UUCP (Rev. Ben A. Mesander) >writes: >>In article loftus@wpllabs.UUCP (William Loftus) >>writes: >>> >>>Does anyone have the specs for the Amiga's object file format? >> >>The documentation for the Amiga object file format, as well as the >>documentation for the dos.library are in the book "The AmigaDOS Manual". > >This information is badly out of date. In particular, it does not contain >SAS's extensions for library indexes and debugging information, which >are used extensively by SAS's and now, I think, others' tools. You can >probably get the spec from either CATS or from SAS directly. >-- >Stephen R. Walton, Dept. of Physics and Astronomy, Cal State Northridge >bcphyagi@csunb.csun.edu until my Suns come back up It isn't out of date. The only real extension to the original documentation is a new small-data hunk and small-data external symbol id. SAS's library indexes are cute but I'm not sure how official they are, and the DEBUGing hunks are SAS/C specific, *NOT* commodore-amiga standard (there is no commodore-amiga standard). Frankly, the library indexes can almost be ignored. It is just as fast to scan the entire library then random access through the directory because you generally hit all the sectors anyway, and random access is less efficient. DLink is as fast or faster than BLink and just uses straight JOIN'd object modules. -Matt -- Matthew Dillon dillon@Overload.Berkeley.CA.US 891 Regal Rd. uunet.uu.net!overload!dillon Berkeley, Ca. 94708 USA