I was actually just talking about this feature with a collegue, and we agreed that access to the compressed tables would be the best case. That way, with a simple build step which parses xml tables to c data structures, we could replace bison's "driver", and access these tables as essentially an opaque external data source. The custom driver would give us flexibility and portability to operate outside of bison's provided framework.
This looks great Wojciech! Should make debugging a bit easier, for sure, and the compressed tables would be wonderful. -Brandon On 8/15/07, Satya <[EMAIL PROTECTED]> wrote: > > Sweetness. How about dumping the parser tables too? we could in theory > build them from the XML automaton, but it would be great if we can get > compressed ones (that Bison outputs to the parser) as part of the > report. > > thanks, > satya. > > On 8/15/07, Wojciech Polak <[EMAIL PROTECTED]> wrote: > > Hello, > > > > I'd like to inform you that the XML Automaton Report task has > > been completed, including the definition of an XML grammar, > > implementation in production, and two XSLT transformations. > > Please visit http://www.gnu.org.ua/~polak/notes/bison-xml-report.html > > for the detailed description. > > > > P.S. This message has been also sent accidentally to help-bison. > > > > Regards, > > Wojciech > > > > > > > > > > > > >
