<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>With older versions of X3DJSAIL,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Of the 15313 Java files in my testing collection, 394 do not compile. The rest compile or have compiled in the past. That’s 96% of the files compile. This does not include files which don’t match the Cp1252 encoding. I have deleted those from my testing collection.</p><p class=MsoNormal>That’s out of 15313 JSON files. Some of these have JSON schema issues or bad URLs. I think that number is 331, so there must be some Java files that don’t come from JSON.</p><p class=MsoNormal><br>I will report on the Java compiler errors next. My initial estimate for the number of errors was 345, which is way below the number of files, so I am thinking perhaps there could be more files which compile, and they were prevented by compilation errors. I am now compiling the files one at a time (actually 8 at a time with “xargs -L 1 -P 8”).</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Once I regenerated the files and recompiled the ones that didn’t compile before, , I got 507 (or 394, more likely, not including existing Java files from X3D resources, which may have classpath issues.) which do not compile, and a total of 2323 outstanding errors, 4-5 per file on average. That’s 96% of the Java files compiling at one point. I still need more work on my serializer, obviously!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I probably need to delete the .class files and start over, but I’m having fun with a bit of statistics!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In other news, 14009 of the class files produced result output JSON files. That’s pretty good! 91% Effort on previously reported X3DJSAIL runtime errors is appreciated! I will now look at the new version! To do: Diff original JSON with new JSON.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This is out of a total of 15651 .x3d input files.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Java that doesn’t compile is here: <a href="http://coderextreme.net/NonCompiledJava.zip">http://coderextreme.net/NonCompiledJava.zip</a> if someone wants to help with the remaining 394 Java files. This archive may disappear (40MB) as it is large.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It would be nice if we could move more of the errors from runtime to compile-time issues if possible (4% compile time and 5% runtime errors), can we do more work on OM4X3D or X3D or X3DJSAIL to make them compile-time? This should be investigated. It may be that my use of the library is more apt to make them runtime issues. Contributions to my JavaSerializerNew.js and associated files are welcome!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</p></div></body></html>