Opened 14 years ago
Closed 10 years ago
#2855 closed Bugs (invalid)
Rapid XML 1.12 whitespace parsing bug
| Reported by: | Chris | Owned by: | Sebastian Redl |
|---|---|---|---|
| Milestone: | Boost 1.42.0 | Component: | property_tree |
| Version: | Boost Development Trunk | Severity: | Problem |
| Keywords: | Cc: |
Description
[My patch, copied from sourceforge.]
Rapid XML 1.12 always skips whitespace following a > (end-of-open-tag) even when parse_trim_whitespace is not specified.
The attached patch skips whitespace following a > ONLY when parse_trim_whitespace IS specified.
Attachments (1)
Change History (7)
by , 14 years ago
| Attachment: | rapidxml.hpp.diff1 added |
|---|
comment:1 by , 13 years ago
| Milestone: | Boost 1.39.0 → Boost 1.40.0 |
|---|
comment:2 by , 13 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:4 by , 11 years ago
This patch really introduced a bug: now, every time a tag is closed, the parser finds after it a non really existent tag with empty name. Unless you activate the option "parse_trim_whitespace", which is intended for other purpose. Since boost uses this library in fact enabling such option, this problem has not been noticed, but anybody directly using rapidxml in boost (property tree may have a huge memory penalty) will find it.
I'd suggest to revert this change, and in case the trim support requires improvement, do it the right way.
comment:5 by , 11 years ago
I don't understand. Can you show an example xml snippet and the expected and actual behavior?
comment:6 by , 10 years ago
| Resolution: | → invalid |
|---|---|
| Status: | assigned → closed |
Given that I have no idea what the problem now is, I'm closing this.
This small patch fixes the problem.