A comparative analysis of how the opensource engines layout their AST nodes could be useful. If there is commonality there could be progress.
Also, it could be left to engine vendors - how or if - they parse JS -> JsonML AST string:- - pure JS - a fallback. No work by vendor. Reuse a JS parser written in JS. - native. Reuse native AST tree walking functionality. Defacto standarization could emerge with this approach. As with json2.js and native JSON. Also, is there a case for a standard function to parse JsonML to JS. Maybe a native implementation - depending on performance compared to pure javascript. N.B: not relevant for narcissus style meta-circular processors. --- _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
