Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!sun-barr!ccut!wnoc-tyo-news!cs.titech!titccy.cc.titech!necom830!mohta
From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
Newsgroups: comp.unix.internals
Subject: Re: Shared Lib Question (ISC)
Message-ID: <187@titccy.cc.titech.ac.jp>
Date: 15 May 91 03:13:00 GMT
References: <162@titccy.cc.titech.ac.jp> <7690@auspex.auspex.com> <169@titccy.cc.titech.ac.jp> <7762@auspex.auspex.com> <184@titccy.cc.titech.ac.jp> <19273@rpp386.cactus.org>
Sender: news@titccy.cc.titech.ac.jp
Organization: Tokyo Institute of Technology
Lines: 36

In article <19273@rpp386.cactus.org>
	jfh@rpp386.cactus.org (John F Haugh II) writes:

>>The problem is that NO OS support shared libraries right, perhaps because
>>there is no way to do so.

>This is trivially false, and the conclusion you reached along with it.

To claim so, he could have simply name a OS which do shared libraries
right, which he don't and perhaps can't do.

>>Indirect jumps and accompanied process private data for the jump table.

>Oh, so you don't like any shared library because it has to use things
>that you don't like?  And this is the basis for your proof that NO OS
>can "support shared libraries right."

Below is the JFH's claim.

	From: jfh@rpp386.cactus.org (John F Haugh II)
	Newsgroups: comp.unix.internals
	Subject: Re: Shared Lib Question (ISC)
	Message-ID: <19252@rpp386.cactus.org>
	Date: 9 May 91 00:00:52 GMT

	Were the code in the C library pure, shared libraries would
	be extremely simple to implement.  Data, which isn't sharable,
	is the worst of the flies in the ointment.

And, as I pointed out, the jump table IS unsharable global data.

>Well, boyo, it's off to the KILL file for you!

Good-bye.

						Masataka Ohta