This is the mail archive of the
libstdc++@sourceware.cygnus.com
mailing list for the libstdc++ project.
Re: Thread-safe libio
- To: libstdc++@sourceware.cygnus.com
- Subject: Re: Thread-safe libio
- From: "Alain Magloire" <alain@qnx.com>
- Date: Mon, 17 May 1999 16:56:16 -0400 (EDT)
>
> "Alain Magloire" <alain@qnx.com> writes:
>
> > If I remember correctly, f{try,un,}lockfile() were introduce *with/for*
> > threading by posix. I did not see any OS that provides flockfile()
> > whitout support for PThreads.
> >
> > flockfile provides opaque reference counting.
>
> First, flockfile was introduced in POSIX but not necessarily for
> PThreads.
Ok I will not argue, but it was my understanding that flockfile,
getc_unlock, putc_lock etc .. was introduce in Posix for threading,
I don't see there usefullness in a single thread.
If you mean that they don't have to be implemented on top of the
propose Posix API threads, Ok.
> Second, I was talking about the interface which is
> available in libio already. It would be a big mistake to introduce
> yet another interface. How the flockfile functions actually must be
> implemented depends on the platform.
Good points. So you're suggesting to use this for I/O only
or for all the stdc++ classes ?
--
au revoir, alain
----
Aussi haut que l'on soit assis, on n'est toujours assis que sur son cul !!!