Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!sdcsvax!ucsdhub!jack!man!crash!ford
From: ford@crash.CTS.COM (Michael Ditto)
Newsgroups: comp.sys.amiga,comp.sys.atari.st,comp.sys.m6809
Subject: Re:  SysVr3 shared libraries and choosing their addresses
Message-ID: <1264@crash.CTS.COM>
Date: Sat, 20-Jun-87 05:12:23 EDT
Article-I.D.: crash.1264
Posted: Sat Jun 20 05:12:23 1987
Date-Received: Mon, 22-Jun-87 05:40:43 EDT
References: <8706040024.AA10895@cogsci.berkeley.edu> <2194@husc6.UUCP> <1221@crash.CTS.COM> <677@nu3b2.UUCP>
Reply-To: ford@crash.CTS.COM (Michael Ditto)
Organization: Crash TS, El Cajon, CA
Lines: 20
Keywords: shared text code libraries UNIX
Summary: Bogus portability
Xref: mnetor comp.sys.amiga:5862 comp.sys.atari.st:4082 comp.sys.m6809:356

In article <677@nu3b2.UUCP> rwhite@nu3b2.UUCP (Robert C. White Jr.) writes:
>Don't just pick an area of memory at random,  The programmers guide contains
>a list of memory areas and what type of function libraries should be
>located in each.
>
>If you go through the list you will find that the list is quite extensive.
>A small degree of care will prevent any overlapping problems.

This is true, but my point was that it requires a human programmer to read
the manual and choose an address each time the program is ported to a new
machine or major OS version.  The recommended addresses will necessarily
be different for different CPU's, MMU's, or OS ports.  It would be much
nicer if there were a way to specify "whatever address works".


-- 

Michael "Ford" Ditto				-=] Ford [=-
P.O. Box 1721					ford@crash.CTS.COM
Bonita, CA 92002				ford%oz@prep.mit.ai.edu