diff options
| author | zlarsen <zlarsen@dmail.dixie.edu> | 2015-10-09 14:07:44 -0600 |
|---|---|---|
| committer | zlarsen <zlarsen@dmail.dixie.edu> | 2015-10-09 14:07:44 -0600 |
| commit | 46b746e8c6101f8a25ba463fb2fb4045c29098a1 (patch) | |
| tree | 688ca286a0ecb9590562504a53fde96c8bbfcd76 /json.html.markdown | |
| parent | 0d0c495c701acc77047df138e169e7cc7ece5f97 (diff) | |
| parent | ef40704f9b66ae85d7a8a6853abbbf8810af3b90 (diff) | |
Merge remote-tracking branch 'adambard/master' into forth-es
Diffstat (limited to 'json.html.markdown')
| -rw-r--r-- | json.html.markdown | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/json.html.markdown b/json.html.markdown index 6aff2ce2..a1629137 100644 --- a/json.html.markdown +++ b/json.html.markdown @@ -10,8 +10,11 @@ As JSON is an extremely simple data-interchange format, this is most likely goin to be the simplest Learn X in Y Minutes ever. JSON in its purest form has no actual comments, but most parsers will accept -C-style (`//`, `/* */`) comments. For the purposes of this, however, everything is -going to be 100% valid JSON. Luckily, it kind of speaks for itself. +C-style (`//`, `/* */`) comments. Some parsers also tolerate a trailing comma +(i.e. a comma after the last element of an array or the after the last property of an object), +but they should be avoided for better compatibility. + +For the purposes of this, however, everything is going to be 100% valid JSON. Luckily, it kind of speaks for itself. ```json { |