SHARED OBJECTS/LIBRARIES

F> From: follis@esd.dl.nec.com (George Follis) > Subject: SHARED OBJECTS/LIBRARIES F> Your statement about a 'shared' library is *wrong* and misleading. Please > go back and re-read the man page and also read the man page on 'mkshlib'. # man mkshlib man: mkshlib: not found in index man: mkshlib: not found It seems that mkshlib is not on (my|every) system. F> After you have done that then you might be better able to answer. There are two interpretations of shared library. In the dictionary, "share" means "to have, use or experience in common". What you are referring to is really best called a "dynamic" library. Sure, it may be called "shared", but that's more confusing. Besides, if you re-read the post I left, my explanation of what ar does and the benefits it provides is NOT misleading. It is clear that the objects created with ar are compiled into the executable. My post also points out the benefits of ar as providing a common repository for objects of which all may not be used in a particular executable. I never even implied that ar created dynamic libraries. If you interpreted that from my post, it's probably because of your understanding that a dynamic library is known as a shared library. So, while it's true that I may have mis-used the word "shared" according to mkshlib, I did not according to the difference between a shared library and a dynamic library, and the usefulness of using ar was well pointed out. F> A library build with 'ar' is not a 'shared' library. F> GRF > -- > -------------------------------------------------------------------------- > The most widely used computer language .... > $*#%"&@+! > -------------------------------------------------------------------------- --- ~ SPEED 1.40 [NR] ~