FGCOM/jansson
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
20efe4aa26
jansson/test/testdata/invalid

179 lines
1.9 KiB
Plaintext
Raw Normal View History

Add some tests
2009-07-10 02:01:40 +08:00
====
1
'[' or '{' expected near end of file
========
null
====
1
'[' or '{' expected near 'null'
========
{
====
2
Streamify the loader It's no longer needed to load the whole input into a string and then parse from the string. Instead, the input is read as needed from a string or file.
2009-07-13 16:01:20 +08:00
string or '}' expected near end of file
Add some tests
2009-07-10 02:01:40 +08:00
========
[
====
2
']' expected near end of file
========
[,
====
1
unexpected token near ','
========
[1,
====
2
']' expected near end of file
========
["a
====
1
Report errors from lexical and stream level in parser Before, only the syntax level (parse_*) was able to set the error string. This patch fixes the situation so that lexical (lex_*) and stream (stream_*) levels can report detailed error messages. Also, instead of 0, EOF is now returned by stream on error.
2009-07-14 04:34:31 +08:00
unexpected newline near '"a'
Add some tests
2009-07-10 02:01:40 +08:00
========
["a"
====
2
']' expected near end of file
========
['
====
1
invalid token near '''
========
{,
====
1
Streamify the loader It's no longer needed to load the whole input into a string and then parse from the string. Instead, the input is read as needed from a string or file.
2009-07-13 16:01:20 +08:00
string or '}' expected near ','
Add some tests
2009-07-10 02:01:40 +08:00
========
{"
====
1
Report errors from lexical and stream level in parser Before, only the syntax level (parse_*) was able to set the error string. This patch fixes the situation so that lexical (lex_*) and stream (stream_*) levels can report detailed error messages. Also, instead of 0, EOF is now returned by stream on error.
2009-07-14 04:34:31 +08:00
unexpected newline near '"'
Add some tests
2009-07-10 02:01:40 +08:00
========
{"a
====
1
Report errors from lexical and stream level in parser Before, only the syntax level (parse_*) was able to set the error string. This patch fixes the situation so that lexical (lex_*) and stream (stream_*) levels can report detailed error messages. Also, instead of 0, EOF is now returned by stream on error.
2009-07-14 04:34:31 +08:00
unexpected newline near '"a'
Add some tests
2009-07-10 02:01:40 +08:00
========
{"a"
====
2
':' expected near end of file
========
{'a'
====
1
Streamify the loader It's no longer needed to load the whole input into a string and then parse from the string. Instead, the input is read as needed from a string or file.
2009-07-13 16:01:20 +08:00
string or '}' expected near '''
Add some tests
2009-07-10 02:01:40 +08:00
========
{"a":
====
2
unexpected token near end of file
========
{"a":"a
====
1
Report errors from lexical and stream level in parser Before, only the syntax level (parse_*) was able to set the error string. This patch fixes the situation so that lexical (lex_*) and stream (stream_*) levels can report detailed error messages. Also, instead of 0, EOF is now returned by stream on error.
2009-07-14 04:34:31 +08:00
unexpected newline near '"a'
Add some tests
2009-07-10 02:01:40 +08:00
========
Expand parser and Unicode test coverage
2009-07-18 20:59:55 +08:00
{"a":"a" 123}
====
1
'}' expected near '123'
========
Add some tests
2009-07-10 02:01:40 +08:00
{[
====
1
Streamify the loader It's no longer needed to load the whole input into a string and then parse from the string. Instead, the input is read as needed from a string or file.
2009-07-13 16:01:20 +08:00
string or '}' expected near '['
Add some tests
2009-07-10 02:01:40 +08:00
========
[{
====
2
Streamify the loader It's no longer needed to load the whole input into a string and then parse from the string. Instead, the input is read as needed from a string or file.
2009-07-13 16:01:20 +08:00
string or '}' expected near end of file
Add some tests
2009-07-10 02:01:40 +08:00
========
[{}
====
2
']' expected near end of file
========
[1,]
====
1
unexpected token near ']'
========
[1,
2,
3,
4,
5,
]
====
6
unexpected token near ']'
========
[1.]
====
1
invalid token near '1.'
========
[1e]
====
1
invalid token near '1e'
========
[1ea]
====
1
invalid token near '1e'
========
[012]
====
1
invalid token near '0'
========
[-012]
====
1
invalid token near '-0'
========
Expand parser and Unicode test coverage
2009-07-18 20:59:55 +08:00
[troo
====
1
invalid token near 'troo'
========
["\a <-- invalid escape"]
====
1
invalid escape near '"\'
========
Add some tests
2009-07-10 02:01:40 +08:00
[" <-- tab character"]
====
1
Report errors from lexical and stream level in parser Before, only the syntax level (parse_*) was able to set the error string. This patch fixes the situation so that lexical (lex_*) and stream (stream_*) levels can report detailed error messages. Also, instead of 0, EOF is now returned by stream on error.
2009-07-14 04:34:31 +08:00
control character 0x9 near '"'
Implement support for \u escapes
2009-07-15 01:47:57 +08:00
========
["\u0000 (null byte not allowed)"]
====
1
\u0000 is not allowed
========
["\uDADA (first surrogate without the second)"]
====
1
invalid Unicode '\uDADA'
========
["\uD888\u3210 (first surrogate and invalid second surrogate)"]
====
1
invalid Unicode '\uD888\u3210'
========
["\uDFAA (second surrogate on it's own)"]
====
1
invalid Unicode '\uDFAA'
Expand parser and Unicode test coverage
2009-07-18 20:59:55 +08:00
========
å
====
1
'[' or '{' expected near 'å'
Reference in New Issue Copy Permalink