--- "Mark J. Stang" <[EMAIL PROTECTED]> wrote: > My only dependency, other than Xindice, is the > parser classes.
It should be the same for a Xindice implementation of SiXDML. Actually maybe not since I'd want to implement schema support and transforms just as I've done in the eXcelon implementation. So there'll probably be dependencies on Xerces and Xalan as well which should be acceptable. > I have heard > great stuff about ANTLR, I just don't know how to > use it. ANTLR is fairly easy to grasp if you have a background in parsing. The SiXDML language implementation is my first time using ANTLR and I learned most of it in less than a week or so. The documentantation could be better about potential gotchas but it so much more powerful than lex & yacc that I soon overlooked any minor gripes that I had. > If we can get a > stack or list of tokens then my code will work with > Xindice from there on > down. I probably don't have as complete an > implementation as you do... Cool, my language parser relies on my API so that work is already done. So what is actually needed is to implement the SiXDML API for Xindice. I'll take a look at your code tomorrow (or is that later today?) and see what I can leverage. PS: What version of Xindice should I use to work on the SiXDML implementation? The version off the web or from CVS? PPS: I don't use JUnit and probably won't have time to learn it so some help with setting up tests may be necessary. ===== LAWS OF COMPUTER PROGRAMMING, VIII Any non-trivial program contains at least one bug. http://www.25hoursaday.com Carnage4Life (slashdot/advogato/kuro5hin) __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com
