On Thu, May 07, 1998 at 08:26:43PM +0100, Glynn Clements wrote:
>
> Seth M. Landsman wrote:
>
> > Okay, this seems like as good a place as any to flaunt my
> > ignorance. So most of my unix programming experience is in minor kernel
> > hacking and lots of self contained project. Because of this background, I
> > don't have a clue of what might be necessary to write a decent, usable
> > shared library. Can someone throw a reference my way?
>
> Are you asking how to compile one, or what to put in it?
The former.
<<- snipping stuff about how to make a shared library ->>
That does answer my question. I do have a follow up. Libraries,
in general, should go out of their way to be reentrant and thread-safe
(I'm hoping the "why" is obvious to the audience on this list, but I'll
go into further detail on the topic if necessary).
So the question on the floor is, what kinds of tricks and gotchas
are there to look out for. I know of a few, but I'm sure my list is not
complete (i.e., avoid globals, and if you must use them, make the
operations atomic)
-Seth
--
"It is by will alone I set my mind in motion"
