|
Boost : |
From: Reece Dunn (msclrhd_at_[hidden])
Date: 2003-12-17 15:44:55
Paul A. Bristow wrote:
>| [mailto:boost-bounces_at_[hidden]]On Behalf Of Reece Dunn
>| Subject: [boost] Output Formatters
>|
>| There has been recent discussion about the similarity between
>serialization
>| and display. In response to this I have implemented an experimental data
>| input mechanism for text-based systems in my library:
>
>|
>boost-sandbox/libs/example/serialize.cpp
>
>Sorry if I am half blind/ inefficient with CVS, but I could not find this
>^^^^^
Oops! The file is:
boost-sandbox/libs/outfmt/example/serialize.cpp
>| I have several questions:
>|
>| [1] Is there a demand for input support of complex/sequential data types
>| from a stream?
>
>Yes, IMO.
Cool! I shall work on it, and let you know what I come up with.
>| [snip]
>| Aside from this addiion, do people feel that my library is ready for
>review.
>Looks promising to me, but I can see that a 'merger' with serialization may
>prove attractive longer-term.
The problem is that my library is tied into the I/O stream library and is
thus a text-based serialization system. For people who want efficient and/or
binary serialization, you would need to go elsewhere.
As far as I can tell serialization libraries like Robert Ramey's are not
built into the C++ I/O library (for efficiency). I may be wrong on this, and
will check up on it.
My feeling is that serialization will split into text-based systems that are
tied into the I/O stream library (like my library) and binary-based systems
that aren't.
Regards,
Reece H Dunn
_________________________________________________________________
Stay in touch with absent friends - get MSN Messenger
http://www.msn.co.uk/messenger
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk