update json_object_new_string_len, json_escape_str (internal). Writer handles \x00 correctly

Added parse_null test. This does not change anything with how the parser handles \u0000 or null characters

This commit is addapted from one by Adomas Paltanavičius <adomas@leanholding.com>



git-svn-id: http://svn.metaparadigm.com/svn/json-c/trunk@63 327403b1-1117-474d-bef2-5cb71233fd97
This commit is contained in:
Jehiah Czebotar
2011-01-14 17:23:06 +00:00
parent a503ee8217
commit ac601b5b5f
7 changed files with 94 additions and 18 deletions

35
test_null.c Normal file
View File

@@ -0,0 +1,35 @@
/*
* Tests if binary strings are supported.
*/
#include <stdio.h>
#include <string.h>
#include "config.h"
#include "json_inttypes.h"
#include "json_object.h"
int main() {
// this test has a space after the null character. check that it's still included
const char *input = " \0 ";
const char *expected = "\" \\u0000 \"";
struct json_object *string = json_object_new_string_len(input, 3);
const char *json = json_object_to_json_string(string);
int strings_match = !strcmp( expected, json);
int retval = 0;
if (strings_match) {
printf("JSON write result is correct: %s\n", json);
printf("PASS\n");
} else {
printf("JSON write result doesn't match expected string\n");
printf("expected string: ");
printf("%s\n", expected);
printf("parsed string: ");
printf("%s\n", json);
printf("FAIL\n");
retval=1;
}
json_object_put(string);
return retval;
}