From: James E. Hopper <jhopper@erinet.com>
Subject: Re: A Text_IO question I never dared to ask...
Date: 1996/07/02
Date: 1996-07-02T00:00:00+00:00 [thread overview]
Message-ID: <4rac4g$pc5@eri2.erinet.com> (raw)
In-Reply-To: Dtvz3C.2q@jvdsys.nextjk.stuyts.nl
> >This is something that has been bugging me for some time, but to
which I >still cannot find a reasonable answer: > > Why is there no
record (or even file) locking in Text_IO ???
Actually the provinzono (spelling??) version of the pthreads that is
used in linux (and now gnat-mac) comes with threadsafe libc. among
the features of which is that the basic stdIO routines used by text_io
are all using lock, unlock calls around them. i am NOT a c or
pthreads expert but since a bug in the latest pthreads beta code made
text edit hang waiting for a missing unlock until i fixed it for the
mac version i suspect they are doing what would be expected of such
routines. i wrote a couple of tasks to intersperce text io between
two competing tasks and they appear to work correctly.
there is what proports to be a threadsafe malloc as part of this code
as well though i havent verified how well it works in a
multiprocessing environemnt at this time. I remember someone on CLA
asking after this for sun.
jim
next prev parent reply other threads:[~1996-07-02 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-01 0:00 A Text_IO question I never dared to ask Jerry van Dijk
1996-07-02 0:00 ` James E. Hopper [this message]
1996-07-03 0:00 ` Jerry van Dijk
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox