no context for syntax error due to a literal TAB in string

[trentm]

peterg noticed this. If a JSON file has a literal tab character in a string, that is invalid syntax. However, json doesn't give context on the error like it does for other cases.

See for the test files: https://gist.github.com/trentm/45940fadbfaace8d2f50

$ json -nf foo.json
json: error: "foo.json" is not JSON: SyntaxError: Unexpected token

$ json -nf comma.json
json: error: "comma.json" is not JSON: Unexpected ']' at line 1, column 16:
        [{"foo":"bar"},]
        ...............^

Why no context on the error in foo.json that has an illegal literal tab in the string?

[trentm]

The json_parse from https://github.com/douglascrockford/JSON-js doesn't balk at the literal TAB. I wonder if it should.

$ ./lib/json.js -nf tab.json
XXX getting detail
XXX json_parse: normBuffer="{\"foo\": \"baa\ttab\"}\n"
XXX json_parse no exception
json: error: "tab.json" is not JSON: SyntaxError: Unexpected token
[09:56:39 trentm@danger0:~/tm/json (master)]
$ ./lib/json.js -nf comma.json
XXX getting detail
XXX json_parse: normBuffer="[{\"foo\":\"bar\"},]\n"
XXX json_parse err { name: 'SyntaxError',
  message: 'Unexpected \']\'',
  at: 16,
  text: '[{"foo":"bar"},]\n' }
json: error: "comma.json" is not JSON: Unexpected ']' at line 1, column 16:
        [{"foo":"bar"},]
        ...............^