Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!homxb!houxm!mhuxt!mhuxm!mhuxo!ulysses!allegra!mit-eddie!husc6!seismo!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.UUCP
Newsgroups: comp.arch,comp.lang.c
Subject: Re: String Handling and run-time libraries
Message-ID: <5724@brl-smoke.ARPA>
Date: Sun, 5-Apr-87 18:58:04 EST
Article-I.D.: brl-smok.5724
Posted: Sun Apr  5 18:58:04 1987
Date-Received: Thu, 9-Apr-87 01:48:36 EST
References: <15292@amdcad.UUCP> <978@ames.UUCP> <15694@sun.uucp> <6042@mimsy.UUCP> <16014@sun.uucp> <291@pembina.alberta.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 17
Xref: utgpu comp.arch:795 comp.lang.c:1491

In article <291@pembina.alberta.UUCP> bjorn@alberta.UUCP (Bjorn R. Bjornsson) writes:
>SVID specifies shared memory.

Since when?

The problem is, shared memory requires adequate support from the
underlying machine architecture and memory management.  Recognizing
this, the SVID (last I looked, my copy is not at hand now) specified
what the shared memory facility must look like IF it is implemented,
but did not require its implementation.

Beyond shared memory, shared libraries require substantial support
from the link editor etc.  Compatibility with existing facilities
may well constraint Sun's ability to implement shared libraries.
Also, are shared libraries important enough to claim a substantial
chunk of their limited development resources?  There are other
important things that also need to be taken care of..