Path: utzoo!utgpu!attcan!uunet!husc6!uwvax!rutgers!mit-eddie!ll-xn!ames!amdahl!kim From: kim@amdahl.uts.amdahl.com (Kim DeVaughn) Newsgroups: comp.sys.amiga Subject: Re: ARP commands--How do you make them so small? Keywords: ARP AmigaDOS Replacement Project Message-ID: Date: 5 Aug 88 01:19:38 GMT References: <441@jc3b21.UUCP> Distribution: na Organization: Amdahl Corporation, Sunnyvale, CA 94086 Lines: 35 In article <441@jc3b21.UUCP>, fgd3@jc3b21.UUCP (Fabbian G. Dufoe) writes: > > He wondered how the ARP commands were kept so small. Many of them are less > than 1K in executable form. The only explanation I could give was that the > commands called routines in a runtime library. Is that correct? Does ARP > require a runtime library or do you just neet the library at compile time? > > Is there anything else that would explain how the programs are kept so > small? Any information would be appreciated. Two reasons for their small size: You got the 1st one ... ARP does indeed use a runtime lib (arp.library), which is 14396 bytes for the current (v1.1) release. Second, all the individual commands (as well as the aforementioned library) are coded in nice tight assembly language. You can use the arp.library function()'s in your code to do a variety of useful things. To do so, you also need to link in the compile time lib's (arp.lib and/or a.lib) with your code, and any required lib's from your compiler vendor. That cover it? /kim -- UUCP: kim@amdahl.amdahl.com or: {sun,decwrl,hplabs,pyramid,uunet,oliveb,ames}!amdahl!kim DDD: 408-746-8462 USPS: Amdahl Corp. M/S 249, 1250 E. Arques Av, Sunnyvale, CA 94086 CIS: 76535,25