From d6497d86f8e1c913c15ba41521b8e16a7ea4826d Mon Sep 17 00:00:00 2001 From: Milo Yip Date: Sun, 6 Jul 2014 22:51:09 +0800 Subject: [PATCH] Update dom.md Fixes diagrams URL in DOM --- doc/dom.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/dom.md b/doc/dom.md index caad770..117469a 100644 --- a/doc/dom.md +++ b/doc/dom.md @@ -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.