> 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, or console or
> > pipe).
>
> Mine isn't connected to the actual medium. It works for yourself (and for
> pipe streams).
>
> > Hence, I'm wondering if it's a good idea to
> > combine the two in a ostream class. I confess I haven't
> > looked at your code, but I think it would be nice if
> > somehow it could be streambuf thread safety could be separated
> > from the {o,i}stream features which are only concerned with
> > formatting. Does that make sense?
>
> Only pipestream is thread safe. Iostreams are not.
I made them thread-safe ;)
Anyway, the point is that I'm interested in iostream-like pipes.
I wanted to download them, but I dunno what the problem was, but could
not convice yahoo to give it to me :(
Will try again later.
Best,
John
>
> --
> Alexander Nasonov
> Remove minus and all between minus and at from my e-mail for timely
response
>
>
> _______________________________________________
> Unsubscribe & other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost
>
>
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
