- From: Robin Berjon <robin@berjon.com>
- Date: Wed, 8 Jun 2011 22:25:48 +0200
- To: Dominique Hazael-Massieux <dom@w3.org>
- Cc: public-script-coord <public-script-coord@w3.org>
On May 25, 2011, at 15:24 , Dominique Hazael-Massieux wrote: > FWIW, a few pointers to existing Web IDL processors with their test > suite (but which mostly address proper syntactic parsing): > * widlproc , a tool that turns Web IDL fragments into XML (and which I > now maintain) http://widl.webvm.net/ > http://widl.webvm.net/svn/widlproc/trunk/test/valid/idl/ > > * esidl , a tool that generates C++ stubs from Web IDL fragments > http://code.google.com/p/es-operating-system/source/browse/ > http://code.google.com/p/es-operating-system/source/browse/#svn%2Ftrunk% > 2Fesidl%2Ftestsuite > > * Whatpm::WebIDL a tool that parses Web IDL fragments and turns them > into Perl objects (used by [2] to generate test cases) > http://suika.fam.cx/www/markup/html/whatpm/Whatpm/WebIDL.html > http://suika.fam.cx/gate/cvs/markup/html/whatpm/Whatpm/WebIDL.pm > http://suika.fam.cx/gate/cvs/markup/html/whatpm/t/webidl/ FWIW there's also webidl.js: https://github.com/darobin/webidl.js. There is currently a stupid bug that prevents it from parsing some of the HTML5 WebIDL, and it needs a few tweaks to be up to speed with the present draft but other than that it works (for me, at least :). It's the IDL parser in ReSpec v2 and so far it's been correct. It returns a JS data structure that represents the AST and could be serialised. -- Robin Berjon - http://berjon.com/ - @robinberjon
Received on Wednesday, 8 June 2011 20:26:12 UTC