- Mar 19, 2015
-
-
Arseny Kapoulkine authored
-
Arseny Kapoulkine authored
-
Arseny Kapoulkine authored
-
- Mar 18, 2015
-
-
Arseny Kapoulkine authored
Previously we omitted extra whitespace for single PCDATA/CDATA children, but in mixed content there was extra indentation before/after text nodes. One of the problems with that is that the text that you saved is not exactly the same as the parsing result using default flags (parse_trim_pcdata helps). Another problem is that parse-format cycles do not have a fixed point for mixed content - the result expands indefinitely. Some XML libraries, like Python minidom, have the same issue, but this is definitely a problem. Pretty-printing mixed content is hard. It seems that the only other sensible choice is to switch mixed content nodes to raw formatting. In a way the code in this change is a weaker version of that - it removes indentation around text nodes but still keeps it around element siblings/children. Thus we can switch to mixed-raw formatting at some point later, which will be a superset of the current behavior. To do this we have to either switch at the first text node (.NET XmlDocument does that), or scan the children of each element for a possible text node and switch before we output the first child. The former behavior seems non-intuitive (and a bit broken); unfortunately, the latter behavior can cost up to 20% of the output time for trees *without* mixed content. Fixes #13.
-
- Mar 14, 2015
-
-
Arseny Kapoulkine authored
data/truncation.xml was corrupted at some point and was not actually valid. Fix the file and make the test fail if we can't parse truncation.xml at all.
-
- Mar 13, 2015
-
-
Arseny Kapoulkine authored
With the current setup it successfully finds the (fixed) DOCTYPE buffer overrun in ~50 minutes (on a single core).
-
Arseny Kapoulkine authored
-
- Mar 10, 2015
-
-
Arseny Kapoulkine authored
This prevents malformed PI value from breaking the document structure.
-
- Mar 05, 2015
-
-
Arseny Kapoulkine authored
Since all string allocations are pointer-aligned to avoid aligning more frequent node allocations, we can rely on that in string encoding. Encoding page offset and block size in sizeof(void*) units increases the maximum memory page size from 64k to 256k on 32-bit and 512k on 64-bit platforms. Fixes #35.
-
Arseny Kapoulkine authored
Remove size=0 test since a better test is already there.
-
Arseny Kapoulkine authored
Also change the error code to status_io_error
-
Arseny Kapoulkine authored
Merge branch 'mloy-master'
-
-
- Mar 04, 2015
-
-
Arseny Kapoulkine authored
Also add new tests for translate. These are technically redundant since other tests would catch the bug with the fixed comparison, but more tests is better.
-
Arseny Kapoulkine authored
The implementations generated a string with an internal null terminator; this went unnoticed since unit test string verification did not perform string equality check properly (it compared XPath string result as a C-string, thus stopping at the first null terminator). Fixes #36.
-
- Mar 02, 2015
-
-
Arseny Kapoulkine authored
Align allocations to right end of page boundary to catch buffer overruns, instead of unmapping on deallocations mark the page as no-access to guarantee a page fault on use-after-free.
-
- Feb 12, 2015
-
-
Arseny Kapoulkine authored
Instead just ignore the result of xargs.
-
Arseny Kapoulkine authored
-
Arseny Kapoulkine authored
This prevents malformed input XML with very deeply recursive DOCTYPE sections from crashing the parser. Fixes #29.
-
- Jan 24, 2015
-
-
Arseny Kapoulkine authored
This removes the last code.google.com reference from documentation.
-
Arseny Kapoulkine authored
The current code is not optimal; since users actually read samples/tests change them to use faster (and shorter!) code.
-
- Jan 18, 2015
-
-
Arseny Kapoulkine authored
Also include math.h to fix issues on some compilers.
-
Arseny Kapoulkine authored
-
- Jan 17, 2015
-
-
Arseny Kapoulkine authored
Also fix the float/double member order in the header file.
-
Arseny Kapoulkine authored
We test min/max and several different mantissas for the entire exponent range for both float and double. It's not clear whether all supported compilers provide an implementation of sprintf/strtod that supports roundtripping so we may need to disable some of these tests in the future.
-
Arseny Kapoulkine authored
These only do basic testing to make sure the paths are covered and trivial values work.
-
Arseny Kapoulkine authored
-
Arseny Kapoulkine authored
Make float/double round-trip This change also adds xml_text::set and xml_attribute::set_value overloads for float so that float is only printed using just enough digits to represent float, instead of enough digits to represent double.
-
Steve Doiel authored
-
- Jan 16, 2015
-
-
Steve Doiel authored
-
Steve Doiel authored
-
- Jan 10, 2015
-
-
Arseny Kapoulkine authored
It's sufficient to define PUGIXML_HEADER_ONLY anywhere now, source is included automatically. This is a second attempt; this time it includes a workaround for QMake bug that caused it to generate incorrect Makefile.
-
- Jan 06, 2015
-
-
Steve Doiel authored
Make float/double round-trip
-
- Dec 14, 2014
-
-
Arseny Kapoulkine authored
Unfortunately, standard headers on MinGW32 insist on undefining off64_t and _wfopen extensions if __STRICT_ANSI__ is true (e.g. C++11 mode). This leads to compilation errors since b7a1fecc started to use _wfopen in strict mode. That change erroneously checked GCC version - however, the version itself is irrelevant; the actual criteria is whether mingw64 runtime is used. off64_t is not useful on MinGW32 since we only need it to open large files on 64-bit platforms; unfortunately, the lack of _wfopen means we won't be able to support wide-char paths on Windows for MinGW32. Fixes #24.
-
- Nov 27, 2014
-
-
Arseny Kapoulkine authored
-
- Nov 26, 2014
-
-
Arseny Kapoulkine authored
-
- Nov 25, 2014
-
-
Arseny Kapoulkine authored
Since MinGW 4.5 does not define these functions if __STRICT_ANSI__ is defined (in case of _wfopen it defines it inconsistently between stdio.h and wchar.h) use the baseline functions for MinGW 4.5 and earlier. Fixes #23.
-
Arseny Kapoulkine authored
-
- Nov 21, 2014
-
-
Arseny Kapoulkine authored
node_copy_string relied on the fact that target node had an empty name and value. Normally this is a safe assumption (and a good one to make since it makes copying faster), however it was not checked and there was one case when it did not hold. Since we're reusing the logic for inserting nodes, newly inserted declaration nodes had the name set automatically to xml, which in our case violates the assumption and is counter-productive since we'll override the name right after setting it. For now the best solution is to do the same insertion manually - that results in some code duplication that we can refactor later (same logic is partially shared by _move variants anyway so on a level duplicating is not that bad).
-
Arseny Kapoulkine authored
Add allow_insert_attribute (similar to allow_insert_child).
-