31 Mar
2016
31 Mar
'16
7:57 a.m.
Hi Christian,
great - and fairly simple.
My proposal would have been to implement a DOM tree builder on the EventHandler interface (where you use XmlSerializer), and that would not require much effort either. It need not necessarily be done in the generated code, but could as well be implemented on top.
I am busy right now, but will be able to present some code tonight.
Is there a different tree model than DOM, that you would prefer for BaseX?
By the way, the generated Saxon imports serve two purposes:
- adapting to the extension function API (necessary when using Saxon-HE) - using Saxon's native tree builder.
Best regards Gunther
--
Gesendet: Donnerstag, 31. März 2016 um 11:14 Uhr
Von: "Christian Grün" christian.gruen@gmail.com
An: "Gunther Rademacher" grd@gmx.net
Cc: BaseX basex-talk@mailman.uni-konstanz.de
Betreff: Re: Re: [basex-talk] BaseX optimizer performance on REx-generated parser
Hi Gunther, hi all,
here is a straightforward (yet I somewhat hacky) way to invoke the ReX
Java parser code from XQuery:
1. download the XQuery grammar, e.g.
http://bottlecaps.de/rex/CR-xquery-31-20151217.ebnf
2. generate a Java-coded parser from it, using these command line options
-java -tree -main
3. compile the result
javac CR_xquery_31_20151217.java
4. run the attached XQuery files with BaseX or Saxon EE, and with the
compiled parser classes in the classpath, e.g.:
java -cp BaseX.jar;. org.basex.BaseX parse-xquery.xq
java -cp saxon9ee.jar;. net.sf.saxon.Query parse-xquery.xq
(The semicolon must be replaced with a colon on Unix/Linux-based systems).
In BaseX, for simple inputs, the compiled tree will be available in
5-10 ms. I assume it could be even faster when embedding some native
BaseX code in the ReX Parser Generator; but I don’t know how much
effort this will be?
Hope this helps, feedback is welcome,
Christian