Timeline for Simple JSON parser in C
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 15, 2017 at 20:56 | comment | added | Harald Scheirich | I totally missed that part of the standard, yes the escape sequences need to be parsed correctly. | |
| Nov 14, 2017 at 19:08 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
added 176 characters in body
|
| Nov 14, 2017 at 19:03 | comment | added | Ilmari Karonen |
OK, fair enough. You should probably still at least decode simple escapes of the form \u00XX, since some encoders might choose to use them even for ASCII characters. (Also, I added a suggestion to mark some of your functions as inline above, since I forgot to do that earlier.)
|
|
| Nov 14, 2017 at 18:59 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
fix variable name, add suggestion to mark simple functions as inline
|
| Nov 14, 2017 at 18:08 | comment | added | Harald Scheirich | Great work, thanks, obviously I didn't check the standard as much as I should have. Although I did disregard utf-8 intentionally (probably should have mentioned that. | |
| Nov 14, 2017 at 13:22 | vote | accept | Harald Scheirich | ||
| Nov 13, 2017 at 22:45 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
added 1127 characters in body
|
| Nov 13, 2017 at 22:15 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
added 229 characters in body
|
| Nov 13, 2017 at 22:03 | history | edited | Ilmari Karonen | CC BY-SA 3.0 |
added 8226 characters in body
|
| Nov 13, 2017 at 7:48 | history | answered | Ilmari Karonen | CC BY-SA 3.0 |