diff options
author | Milo Yip <miloyip@gmail.com> | 2014-07-06 18:51:09 +0400 |
---|---|---|
committer | Milo Yip <miloyip@gmail.com> | 2014-07-06 18:51:09 +0400 |
commit | d6497d86f8e1c913c15ba41521b8e16a7ea4826d (patch) | |
tree | dcc12f9d3e6fe91cd5b39dff61dc949268e9b5e9 /doc | |
parent | bcd935be875353af3538253a3a282b475c71f0c4 (diff) |
Update dom.md
Fixes diagrams URL in DOM
Diffstat (limited to 'doc')
-rw-r--r-- | doc/dom.md | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -166,11 +166,11 @@ In normal parsing process, a large overhead is to decode JSON strings and copy t The following diagrams compare normal and *in situ* parsing. The JSON string values contain pointers to the decoded string. -![normal parsing](diagrams/normalparsing.png) +![normal parsing](diagram/normalparsing.png) In normal parsing, the decoded string are copied to freshly allocated buffers. `"\\n"` (2 characters) is decoded as `"\n"` (1 character). `"\\u0073"` (6 characters) is decoded as "s" (1 character). -![instiu parsing](diagrams/insituparsing.png) +![instiu parsing](diagram/insituparsing.png) *In situ* parsing just modified the original JSON. Updated characters are highlighted in the diagram. If the JSON string does not contain escape character, such as `"msg"`, the parsing process merely replace the closing double quotation mark with a null character. @@ -264,4 +264,4 @@ d.Parse(json); If the total size of allocation is less than 1024 during parsing, this code does not invoke any heap allocation (via `new` or `malloc()`) at all. -User can query the current memory consumption in bytes via `MemoryPoolAllocator::Size()`. And then user can determine a suitable size of user buffer.
\ No newline at end of file +User can query the current memory consumption in bytes via `MemoryPoolAllocator::Size()`. And then user can determine a suitable size of user buffer. |