Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!snorkelwacker!apple!sun-barr!newstop!texsun!texbell!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.tech Subject: Re: I need Help with the A3000! Message-ID: <6142@sugar.hackercorp.com> Date: 4 Aug 90 00:06:35 GMT References: <6071@sugar.hackercorp.com> <13386@cbmvax.commodore.com> <6091@sugar.hackercorp.com> <1990Jul25.224140.24184@cbnewsm.att.com> <13456@cbmvax.commodore.com> <6100@sugar.hackercorp.com> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Distribution: comp Organization: Sugar Land Unix - Houston Lines: 18 In article rimajpuz@watsol.uwaterloo.ca (Rick I. Majpruz) writes: > With shared libraries the object code can be loaded at runtime. And a > given piece of object code is loaded only once no matter how many > applications use it. Well, with a minimum of one copy per client node. And the application on the client is still responsible for managing update events, menus, and so on. Must be fun in a compute-intensive program. > But by compiling with sharable libraries, > the executable is only 48K. This compares with 32K for the stdio `hello > world': apparently Sun O/S uses 16K segments in the executables. So the stdio "hello world" would be smaller if it didn't use shared libraries? What an odd result, but I suppose it makes sense. -- Peter da Silva. `-_-' .