Re:[boost] Re: Re: iostreams library review
Question, have you tried to combine the streaming with boost serialization?
I think Robert Ramey has already done the work to combine serialization with iostreams, since his archive types are constructible from arbitrary streams -- that means it's already possible to create archives based on streams from the iostreams library, e.g. memory-mapped file streams.
There may be other interactions I haven't considered. I've only read the documentation; I haven't actually tried to use the serialization library yet.
The serialization library archives use streams and make no special assumptions regarding them. It works with all the streams I've happened to try. I will be taking a close look at the iostreams library proposal. In the course of implementing the serialization library I've had to become much more familiar with locales, facets, codecvt, element types, EOF, etc than I wanted to. Oh - and that fact that different versions of the standard library have myriad minor quirks that have to be considered. This was necessary in order to avoid dependence on the stream in the wrong way. I'm very interested in this but have come to the conclusion that there might be more here than meets the eye. - Of course that's why we have the review process. Robert Ramey
Question, have you tried to combine the streaming with boost serialization?
I think Robert Ramey has already done the work to combine serialization with iostreams, since his archive types are constructible from arbitrary streams -- that means it's already possible to create archives
streams from the iostreams library, e.g. memory-mapped file streams.
There may be other interactions I haven't considered. I've only read the documentation; I haven't actually tried to use the serialization
yet.
The serialization library archives use streams and make no special assumptions regarding them. It works with all the streams I've happened to try. I will be taking a close look at the iostreams library
the course of implementing the serialization library I've had to become much more familiar with locales, facets, codecvt, element types, EOF, etc
"Robert Ramey" <ramey@rrsd.com> wrote in message news:20040602150743.00E3231473@acme.west.net... based on library proposal. In than I
wanted to.
Tell me about it ;-)
Oh - and that fact that different versions of the standard library have myriad minor quirks that have to be considered.
I found that STLPort gave me the most trouble. The straightforward way to implement putpack simply doesn't work. Also random access in file streams is a bit quirky in STLPort and libcomo.
This was necessary in order to avoid dependence on the stream in the wrong way. I'm very interested in this but have come to the conclusion that there might be more here than meets the eye.
It wouldn't surprise me a bit. Jonathan
participants (2)
-
Jonathan Turkanis -
Robert Ramey