Alexander Nasonov [EMAIL PROTECTED] writes:
Philippe A. Bouchard wrote:
There is another pipestream project you can take a look at:
http://pstreams.sourceforge.net/
May be I missed something but this library is about reading from stdin and
writing to stdout of other process. It's not
graydon hoare wrote:
an inter-thread pipe might also be referred to as a synchronization
channel, if you want to avoid confusion about names (pipes being a
particular OS object).
-graydon
Synchronization channel sounds good except that stream names are too long.
synchronization_channel
Larry Evans wrote:
[snip]
indicating some interest in combining thread safety and
decoration. It seems to me (a novice in threading) that
what needs to be protected is the access to the end
of the pipeline, i.e. the final streambuf, which is
connected to the actual output medium
Alexander Nasonov [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
graydon hoare wrote:
an inter-thread pipe might also be referred to as a synchronization
channel, if you want to avoid confusion about names (pipes being a
particular OS object).
-graydon
Synchronization
Alexander Nasonov wrote:
All of you know what is pipe and what are iostreams. In this library
they work together.
Writer-thread put objects into pipes while reader-thread get them
from the pipe. Ålthough objects are copied to/from pipe, this is
often a better alternative to object sharing
Philippe A. Bouchard wrote:
There is another pipestream project you can take a look at:
http://pstreams.sourceforge.net/
May be I missed something but this library is about reading from stdin and
writing to stdout of other process. It's not about inter-thread pipes.
--
Alexander Nasonov
Bohdan wrote:
Alexander Nasonov [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
graydon hoare wrote:
an inter-thread pipe might also be referred to as a synchronization
channel, if you want to avoid confusion about names (pipes being a
particular OS object).
-graydon
Philippe A. Bouchard [EMAIL PROTECTED] writes:
There is another pipestream project you can take a look at:
http://pstreams.sourceforge.net/
There was also another former implementation in the Gnu Gcc lib but it was
discarded, I don't know why.
I have a unix-only sort of work in progress
Larry Evans wrote:
[snip]
indicating some interest in combining thread safety and
decoration. It seems to me (a novice in threading) that
what needs to be protected is the access to the end
of the pipeline, i.e. the final streambuf, which is
connected to the actual output medium (a file,
http://lists.boost.org/MailArchives/boost/msg46513.php
indicating some interest in combining thread safety and
decoration. It seems to me (a novice in threading) that
what needs to be protected is the access to the end
of the pipeline, i.e. the final streambuf, which is
connected to the
10 matches
Mail list logo
