[x3d-public] JSON parsing, development files

[John Carlson]

Note there is some difference in JSON parsing that we may need to track 
down:

coderextreme at coderextreme-Kubuntu20:~/x3dschema$ grep Failed results.txt 
|grep -v node_modules
Failed JSON parse 
/c/x3d-code/www.web3d.org/x3d/content/examples/Basic/development/TestRegularExpressionChecks.json 
SyntaxError: Unexpected token . in JSON at position 3388
Failed JSON parse 
/c/x3d-code/www.web3d.org/x3d/content/examples/Basic/development/TestDiagnosticOverloadedChildNodes.json 
SyntaxError: Unexpected token { in JSON at position 2494
Failed JSON parse 
/c/x3d-code/www.web3d.org/x3d/content/examples/Basic/development/TestSchematronDiagnostics.json 
SyntaxError: Unexpected token a in JSON at position 23399


coderextreme at coderextreme-Kubuntu20:~/x3dschema$ grep json-parse 
javaresults.txt |grep -v node_modules
json-parse json Expected a ':' after a key at 2621 [character 24 line 
85] 
/c/x3d-code/www.web3d.org/x3d/content/examples/Basic/development/TestDiagnosticOverloadedChildNodes.json
json-parse json Expected a ':' after a key at 32609 [character 24 line 
1198] 
/c/x3d-code/www.web3d.org/x3d/content/examples/Basic/development/TestSchematronDiagnostics.json


I recommend using jsonlint to get down to details about errors in JSON 
parsing.   I know vim is broken on Linux now, I don't know how to go to 
nth character anymore (help?).


Thanks,


John