I haven't seen that, but I have seen a '\0' passed into an assertion
ending up in the XML as-is. I don't even know if that's valid XML or
not, but Hudson's XUnit plugin cannot handle it. Of course I could get
around it, but would it be reasonable to request that the default
behavior of that formatter be to show the hex codepoint or something
rather than the character itself for those characters that are iscntrl
or some such?
On Wed, Jun 9, 2010 at 2:26 PM, Gennadiy Rozental
Gaurav N Shah
writes: Hi,
I have written my own struct to customize logging from struct "boost::unit_test::output::xml_log_formatter"
However, the XML file generated by log Formatter is Invalid. it adds invalid node end = "" , by the end of each test case logging.
Is it possible your formatter does this?
How your struct customizes xml_log_formatter? It does not really have any means of customization. Did you inherit from it?
Gennadiy
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users