A couple of small observations: a.. Test cases for both json_iarchive, json_oarchive and json_om and a complete test case to demonstrate the functionality of all the components. Note that these already exist. All the tests in the library work with all archive types. So any new archive class can (and should be) tested against all test cases. I believe that this is described in the manual. json_iarchive: This is the JSON input archive for Boost.serilization which is based on Boost.Spirit. This is similar to an input data stream and json_iarchive is capable of loading data from a given JSON format to the JSON object model. This sentence seems to suggest that any JSON data file will be readable. In fact, only those generated by the serialization library, though they will be in JSON format, will be readable. This is a very common misconception on the part of those with ambitions to make a new archive class. So maybe this sentence needs to be re-worked to clarify this. Robert Ramey Kasun Indrasiri wrote:
Hi all,
I have published the draft proposal for JSON Archives for Boost.serialization on the following google page.
http://kasun147.googlepages.com/jsonarchivesforboost.serialization
<http://kasun147.googlepages.com/jsonarchivesforboost.serialization>Waiting forward for the comments on the proposal.
Regrads,
Kasun Indrasiri. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost