| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
tests (now that we always rep integers in 64bit entities regardless of arch word size)
|
| |
|
|
|
|
| |
an imperative, while the former might be confused for a question.
|
|
|
|
| |
have a yajl_XXX_config() function that accepts varargs so that configuration is simple, and new config options can be added in the future that preserve backwards binary compatibility. closes #23.
|
| |
|
| |
|
|
|
|
| |
closes #7
|
|
|
|
| |
*forbid* garbage
|
| |
|
|
|
|
| |
Signed-off-by: Lloyd Hilaiel <lloyd@hilaiel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- remove yajl_status_parse_incomplete, replace with three
flag settings
- yajl_allow_multiple_values
- yajl_forbid_trailing_garbage
- yajl_forbid_partial_values
In the new model, callers must consistently call yajl_parse_complete
and check it's return. Two new parse errors have been introduced:
"premature EOF" and "trailing garbage".
yajl_test.c demonstrates the simplifying effect on calling code.
adds 3 flags to yajl_test
-g forbids trailing garbage
-p forbids partial values
-m allows multiple values to be parsed.
and complementary tests.
lth: Addresses the majority of issue #24. gno is awesomesauce.
Signed-off-by: Lloyd Hilaiel <lloyd@hilaiel.com>
|
|\ |
|
| | |
|
|\ \
| |/ |
|
| |
| |
| |
| | |
running 'echo -n' under /bin/sh outputs the '-n' rather than parsing it as an argument which means "omit trailing newline"
|
| |
| |
| |
| | |
Signed-off-by: Lloyd Hilaiel <lloyd@hilaiel.com>
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
| |
installed. Also, on Ubuntu, when I explicitly set the build output
directory, the tests don't run because the run_tests.sh script assumes
that ../build is where the build output directory is.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
longs are 64bit wide, at least on eGLibc/Linux/AMD64, therefore 2^31 is
not an integer overflow.
I've removed the integer overflow because the exact limit is machine
dependent and as far as I've seen the RFC doesn't make any assumptions
towards minimum/maximum width of integers.
|
| |
|
| |
|
|
|
|
| |
across systems (msys+win32 being the problem child)
|
|
|
|
|
|
|
|
|
| |
* bump yajl version to 1.0.0
* update TODO list, removing completed tasks
* update yajl_test to override allocation routines and count allocations/frees, providing an automated standalone way to validate we're not leaky
* update all copyright dates
* update all .gold files with new test output
* update ChangeLog in preparation for 1.0.0 release
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add new parser function, yajl_parse_complete(). This is defined
to parse any buffered data assuming that there is no more input
forthcoming and may issue callbacks based on that parse.
- Implement this as parsing a single space character. This is
sufficient to handle the problem case, a number at the end
of the stream.
- Updated yagl_test.c to call this when the stream ends.
|
|
|
|
|
| |
doesn't interpret this as an error it should handle, but something
that the higher level code should deal with in its representation.
|
|
|
|
|
|
|
|
| |
These succeed right now, but that seems questionable since the the following
character is part of the same token. A failure *would* be issued if the
parser knew that the stream was at an end, I think. Still, the user of
the library might erroneously handle the null/true/false when yajl could
emit the error sooner.
|
| |
|
| |
|
|
|
|
| |
This is useful for integrating with non-cmake build systems such as Xcode.
|
| |
|
|
|
|
| |
warnings
|
|
|
|
| |
number @ eof bug and a testcase to demonstrate the problem.
|
|
|
|
|
|
|
| |
precision numbers in JSON data.
git-svn-id: http://yajl-c.googlecode.com/svn/trunk@102 e775cfb5-b74b-0410-aad5-5bebe4a96390
|
|
|
|
| |
git-svn-id: http://yajl-c.googlecode.com/svn/yajl/trunk@96 e775cfb5-b74b-0410-aad5-5bebe4a96390
|
|
|
|
| |
git-svn-id: http://yajl-c.googlecode.com/svn/yajl/trunk@95 e775cfb5-b74b-0410-aad5-5bebe4a96390
|
|
|
|
| |
git-svn-id: http://yajl-c.googlecode.com/svn/yajl/trunk@94 e775cfb5-b74b-0410-aad5-5bebe4a96390
|
|
|
|
|
|
|
| |
familiar top level make targets.
git-svn-id: http://yajl-c.googlecode.com/svn/yajl/trunk@87 e775cfb5-b74b-0410-aad5-5bebe4a96390
|
|
|
|
| |
git-svn-id: http://yajl-c.googlecode.com/svn/yajl/trunk@78 e775cfb5-b74b-0410-aad5-5bebe4a96390
|
|
|
|
|
|
|
|
| |
constantly stress stream parsing (use a parse buffer ranging in size
from 1 to 32 bytes)
git-svn-id: http://yajl-c.googlecode.com/svn/yajl/trunk@77 e775cfb5-b74b-0410-aad5-5bebe4a96390
|
|
|
|
| |
git-svn-id: http://yajl-c.googlecode.com/svn/yajl/trunk@67 e775cfb5-b74b-0410-aad5-5bebe4a96390
|
|
|
|
| |
git-svn-id: http://yajl-c.googlecode.com/svn/yajl/trunk@64 e775cfb5-b74b-0410-aad5-5bebe4a96390
|
|
|
|
| |
git-svn-id: http://yajl-c.googlecode.com/svn/yajl/trunk@63 e775cfb5-b74b-0410-aad5-5bebe4a96390
|
|
git-svn-id: http://yajl-c.googlecode.com/svn/yajl/trunk@60 e775cfb5-b74b-0410-aad5-5bebe4a96390
|