summaryrefslogtreecommitdiffhomepage
path: root/json.html.markdown
diff options
context:
space:
mode:
authorTodd M. Guerra <toddguerra@gmail.com>2015-10-09 11:14:29 -0400
committerTodd M. Guerra <toddguerra@gmail.com>2015-10-09 11:14:29 -0400
commitfc3c56ee938dbb7231127465b0e9ab5fa7f2da40 (patch)
tree444181fbb299567b566a038ab4241e31ca519a97 /json.html.markdown
parent6d3f52b7f01409818853de6148abf1d8fe57fab0 (diff)
parentdcd9093d6467166a2946008c55f5e0582a15e20c (diff)
Merge remote-tracking branch 'adambard/master'
Conflicts: java.html.markdown
Diffstat (limited to 'json.html.markdown')
-rw-r--r--json.html.markdown7
1 files changed, 5 insertions, 2 deletions
diff --git a/json.html.markdown b/json.html.markdown
index 6aff2ce2..a85cecc4 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
{