Opened 11 years ago
Closed 5 years ago
#6261 closed Bugs (wontfix)
Missing uuid_io.hpp in uuid_serialize.hpp
Reported by: | Owned by: | James E. King, III | |
---|---|---|---|
Milestone: | To Be Determined | Component: | uuid |
Version: | Boost 1.48.0 | Severity: | Not Applicable |
Keywords: | Cc: |
Description
Probably it is not a bug, but my misunderstanding the conception.
Suppose we want to serialize uuid using boost::serialization library through text_[io]archive. If we include only uuid_serialize.hpp and uuid.hpp headers we will get "strange" (particularly for me) compilation error. I found out that the error was omission uuid_io.hpp header: archive class uses iostream operations for serialization.
So the question will be: is it correct to not include uuid_io.hpp into uuid_serialize.hpp header?
Thank you.
Change History (4)
comment:1 by , 11 years ago
comment:2 by , 5 years ago
Given this has been open for 6 years and there have been no further comments, I would recommend closing this as "No Plan to Fix" or "Invalid".
comment:3 by , 5 years ago
Owner: | changed from | to
---|
comment:4 by , 5 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Hmm, I understand what you are saying. Normally the serialization library would use specific functions written for a class. I do not believe that uuid_io.hpp is needed when using a binary archive.
I wanted to make uuid a primitive, i.e. BOOST_CLASS_IMPLEMENTATION(uuid, boost::serialization::primitive_type) (see http://www.boost.org/doc/libs/1_48_0/libs/serialization/doc/index.html). I now wonder if this may have been a bad decision. Or maybe I should have done it via boost::serialization::is_bitwise_serializable. My goal was to use only 16 bytes when serializing to a binary archive.