-
Sorry, I have a mistake.
I attach the bug-fixed diff file.
2009-10-16 07:49:37 UTC by cielquis
-
When RapidXml parses the following XML (parse flag is 0),
the text of data node is empty.
I tried to modify the code to preserve the whitespace
when parse_trim_whitespace is not set.
2009-10-14 07:35:56 UTC by cielquis
-
I had a problem to compile the rapidxml. because this part of code. I change and works... Theoretically, these two version are accepted by the vc 2005. but... I dont know why, only in the second version works.
Version with compiler problems...
alloc_func *m_alloc_func; // Allocator function, or 0 if default is to be used
free_func *m_free_func;.
2009-10-02 00:36:23 UTC by weblucas
-
When parse utf-16 xml text, it sometimes fail.
In attribute_value_pure_pred::test() function, rapidxml lookup the table.
if 'Ch' is wchar_t and 'ch' is 51200(0xC800), then it should return 1,
but it return 0! Because static_cast(51200) is '0'
------------
template
struct attribute_value_pure_pred
{
static unsigned...
2009-10-01 07:20:56 UTC by killrain
-
We do create an XML document containing nodes with child nodes and a value.
print_element_node checks whether the node to be printed has children (rapidxml_print.hpp line 266).
In this case the children are being processed and the value is being ignored.
We added a call to copy_and_expand_chars() similar to line 270 to this case and it worked fine. I'm not sure whether this is a good...
2009-09-25 09:33:26 UTC by mloy
-
When compiling a project using g++ w/ compiler flags -Wall and -Werror, compilation fails for the following function:
template inline OutIt print_attributes(OutIt out, const xml_node *node, int flags)
Correction is as simple as removing the unused flags variable name. i.e.:
template inline OutIt print_attributes(OutIt out...
2009-09-03 16:55:04 UTC by scott_bailey
-
This is a significant problem. Take, for instance, a routine which is designed to copy an arbitrary XML tree to a different document. To support both destructively-parsed and non-destructively-parsed trees, and for efficiency, such a routine will need to call allocate_string() with a length parameter. But if the source tree contains strings with zero length that are not NULL terminated, all...
2009-08-17 19:05:40 UTC by nobody
-
So, as was writtend above to fix this bug we should supply ostream_iterator() ctor with the second template artument (instead of using the default ‘char’ argument):
//..print(std::ostream_iterator(out), node, flags); //
2009-07-18 10:26:48 UTC by alexmission
-
Hello.
For a while I just could not successfully compile the code like:
xml_document< wchar_t > doc; // ok
:
doc.parse( src ) ; // ok
:
std::wcout
2009-07-16 11:07:26 UTC by alexmission
-
Hello.
It seems that in <wchar_t> mode “UTF-8 handling” is pointless IAC. Therefore it would be better to allow the compiler to optimize out the UTF-8 code disregarding the state of the flag ‘parse_no_utf8’. What we need for that is only add a check: sizeof(Ch) > 1, like this:
[code]
| template<int Flags>
| static void insert_coded_character(Ch *&text...
2009-07-16 06:57:54 UTC by alexmission
