Re: SHARED OBJECTS/LIBRAR

In article <3u7ob4$8h1@cssun.mathcs.emory.edu>, timothy.hood@sltrib.com wrote: > >T> From: tschaefe@gate.net (Tim Schaefer) > > Subject: Re: SHARED OBJECTS/LIBRARIES > > Date: 8 Jul 1995 03:03:20 GMT > > Organization: The Computer Business Company, Inc. > > To: informix-list@rmy.emory.edu > >T> In article <3tf9ha$nfk@cssun.mathcs.emory.edu>, timothy.hood@sltrib.com wro >e: >> >>M> Subject: shared objects/libraries >> >>M> Is there anyone out there who has managed to create >> > shared libraries or/and objects with informix source code ??? >> >>A few of us wrestled with the idea recently, and decided on this approach >>(which only works with C version, alas): >> >T> [snipped for brevity] > >>Hope this helps/spawns a worthy discussion. >> >>Tim >> >T> Tim > >T> I use the same method you described in your article. But I'm confused, or > > should I say, ignorant, about the term "shared" libraries. I use libraries > > as described, but are these to be synonomous with "shared libraries"? > >T> Thanks in advance, > >T> Tim > >Tim (S): > >The Unix man page on ar mentions that it is used to maintain libraries, I >have extended that to infer "shared" libraries, since a primary benefit of >putting objects in libraries is their re-use among other executables. > >I think of libraries the same as "shared libraries". > >Tim (H) >--- > ~ SPEED 1.40 [NR] ~ Tim, But as I'm sure you're now aware after some research :-) that shared libraries are more than an attempt at being a nice person. You can share libaries created with ar, if you're a nice person. You HAVE to share shared libraries, or the program won't run. But I would figure you're probably a nice person, and have been sharing so much you didn't see the difference. :-) As I've posted, library usage is a good thing. I have seen lately that you can get into some real problems when more than one release of a product exists on multiple platforms and environments. It CAN be managed, but the best direction is one where you plan ahead. Problems can be easily created when libraries are not named according to software release, and no procedure for who is going to maintain them. As developers are writing code, they come up with new routines and want them to be a part of the library, or change the libary. This is where problems start, so cheap advice is to plan ahead. :-) -- \\\\|// (O|O) ==============================---o00--(_)--00o---============================ Tim Schaefer tschaefe@gate.net http://www.gate.net/~tschaefe People who don't make anything cain't buy anything...never forget that. -HRP =============================================================================