Fundamental defect of the concept of shared libraries

[Masataka Ohta]

In article <7974 at auspex.auspex.com>
	guy at auspex.auspex.com (Guy Harris) writes:

>>You may remember that the speed of Bnews was actually improved by
>>in-lining the first part of strcmp(). In-lining of functions in
>>shared libraries is, of course, impossible.

>Well, in the version of Bnews we have here, that in-lining is done with
>a "STRCMP()" macro, that checks the first two characters and, only if
>they're not equal, calls "strcmp()".

Yes, of course. Bnews is the real example showing significance of call
overhead.

>Our Bnews programs are dynamically linked, and they have that in-lining;
>"In-lining of functions in shared libraries" is, of course, *NOT*
>"impossible", as demonstrated by that.

STRCMP() is source code level inlining of strcmp(), *NOT* strcmp()
in a shared library.

>Perhaps you want to completely delete the Bnews example, as it doesn't
>bolster your case,

Not at all.

						Masataka Ohta