From: Philipp Gesang <Philipp.Gesang@alumni.uni-heidelberg.de>
To: ConTeXt ML <ntg-context@ntg.nl>
Subject: [util-jsn] incorrect handling of escapes
Date: Mon, 8 Jul 2013 00:56:29 +0200 [thread overview]
Message-ID: <20130707225628.GA7955@phlegethon> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 372 bytes --]
Hi,
the JSON parser handles backslash escapes improperly. Example:
local data = [[ { "escapes" : "(\")(\\)(\b)(\f)(\n)(\r)(\t)",
"invalid" : "\'\v" } ]]
local stuff = utilities.json.tolua (data)
inspect(stuff)
Currently it chokes on double quotes and treats the other escapes
like Lua. Fix suggestion attached.
Best regards,
Philipp
[-- Attachment #1.1.2: util-jsn.patch --]
[-- Type: text/x-diff, Size: 1594 bytes --]
--- util-jsn.lua.orig 2013-07-08 00:09:21.834400224 +0200
+++ util-jsn.lua 2013-07-08 00:54:25.889668771 +0200
@@ -15,7 +15,7 @@
-- Reminder for me: check usage in framework and extend when needed. Also document
-- it in the cld lib documentation.
-local P, V, R, S, C, Cc, Cs, Ct, Cf, Cg = lpeg.P, lpeg.V, lpeg.R, lpeg.S, lpeg.C, lpeg.Cc, lpeg.Cs, lpeg.Ct, lpeg.Cf, lpeg.Cg
+local P, V, R, S, C, Cc, Cs, Ct, Cf, Cg, Cp = lpeg.P, lpeg.V, lpeg.R, lpeg.S, lpeg.C, lpeg.Cc, lpeg.Cs, lpeg.Ct, lpeg.Cf, lpeg.Cg, lpeg.Cp
local lpegmatch = lpeg.match
local format = string.format
local utfchar = utf.char
@@ -42,7 +42,15 @@
local whitespace = lpeg.patterns.whitespace
local optionalws = whitespace^0
-local escape = C(P("\\u") / "0x" * S("09","AF","af")) / function(s) return utfchar(tonumber(s)) end
+local escape_a = C(P("\\u") / "0x" * S("09","AF","af")) / function(s) return utfchar(tonumber(s)) end
+local escape_b = P([[\]]) / "" * S([["\/]]) --> represent themselves
+local escape_c = P([[\b]]) / "\010" --> backspace
+ + P([[\f]]) / "\014" --> form feed
+ + P([[\n]]) / "\n"
+ + P([[\r]]) / "\r"
+ + P([[\t]]) / "\t"
+local invalid = P([[\]]) / "" * (Cp() * P(1) / function (pos, chr) --[[ bug_user_about_invalid_escape (chr, pos) ]] return "" end)
+local escape = escape_a + escape_b + escape_c + invalid
local jstring = dquote * Cs((escape + (1-dquote))^0) * dquote
local jtrue = P("true") * Cc(true)
local jfalse = P("false") * Cc(false)
[-- Attachment #1.2: Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2013-07-07 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 22:56 Philipp Gesang [this message]
2013-07-08 16:18 ` Hans Hagen
2013-07-09 9:37 ` Philipp Gesang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130707225628.GA7955@phlegethon \
--to=philipp.gesang@alumni.uni-heidelberg.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).