Opened 12 years ago
Closed 12 years ago
#4429 closed Bugs (fixed)
XML serialization <item_version> appears as character rather than e.g. 0
Reported by: | Owned by: | Robert Ramey | |
---|---|---|---|
Milestone: | Boost 1.44.0 | Component: | serialization |
Version: | Boost 1.44.0 | Severity: | Regression |
Keywords: | xml serialization item_version 0 value | Cc: |
Description
In previous versions (tested with 1.42) serializing e.g. a container using XML gave:
<osnr class_id="6" tracking_level="0" version="0">
<count>3</count> <item_version>0</item_version> <item class_id="7" tracking_level="0" version="0">
..
Using boost trunk, <osnr class_id="5" tracking_level="0" version="0">
<count>0</count> <item_version>@</item_version>
</osnr>
In both cases: <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <!DOCTYPE boost_serialization> <boost_serialization signature="serialization::archive" version="7"> <g class_id="0" tracking_level="0" version="0">
Maybe needs a cast?
System: Debian GNU/Linux GCC 4.4.3 or 4.5 2.6.32
Thank you in advance R.
Change History (4)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
BTW - On my cygwin gcc setup I have one test that fails - test_utf8_codecvt. I'm guessing that something is out of whack with the way codecvt is used/implemented that only shows up with certain compilers/libraries.
Keep up the good work.
Robert Ramey
comment:3 by , 12 years ago
Let me know if I can be of any help in testing, etc. My environment is just debian/ubuntu with gcc 4.3 or 4.5.
Thank you for your prompt reaction and for Serialization in general :) R.
comment:4 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
This would be a huge problem.
And I've confirmed it.
I'm looking into it.
Thanks for catching this in advance of 1.44 release.
Robert Ramey