[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: --no-parser options
From: |
Joel E. Denny |
Subject: |
Re: --no-parser options |
Date: |
Sat, 11 Aug 2007 21:13:00 -0400 (EDT) |
On Tue, 7 Aug 2007, Hans Aberg wrote:
> On 6 Aug 2007, at 22:53, Satya wrote:
>
> > Not too long ago (summer 2006 :) we had a long discussion about
> > dumping the parser tables so that other programs (I wanted to do a
> > visual grammar debugger) can use them. I even put forward a (possibly
> > dumb/simplistic) XML representation of the .output file. But there
> > wasn't any feedback on that. I am not an expert in XML, but if someone
> > proposes a good schema I can add the required code to Bison.
>
> This is just question of writing a new skeleton file, and the code is
> essentially there, though generating in the form C/C++ arrays. But first just
> strip all macros except what generates those arrays, then make another output
> format, if needed.
Currently, generating the .output is more complicated than just printing
out some existing muscles. Glance through print.c to see what I mean.
- --no-parser options, tim, 2007/08/01
- Re: --no-parser options, Joel E. Denny, 2007/08/03
- Re: --no-parser options, tim, 2007/08/03
- Re: --no-parser options, Joel E. Denny, 2007/08/04
- Re: --no-parser options, tim, 2007/08/05
- Re: --no-parser options, Joel E. Denny, 2007/08/05
- Re: --no-parser options, Satya, 2007/08/06
- Re: --no-parser options, Hans Aberg, 2007/08/07
- Re: --no-parser options,
Joel E. Denny <=
- Re: --no-parser options, Hans Aberg, 2007/08/12
- Re: --no-parser options, Joel E. Denny, 2007/08/11
- Re: --no-parser options, Hans Aberg, 2007/08/05
- Re: --no-parser options, tim, 2007/08/06
- Re: --no-parser options, Hans Aberg, 2007/08/06
- Re: --no-parser options, tim, 2007/08/12
- Re: --no-parser options, Hans Aberg, 2007/08/12
- Re: --no-parser options, Satya, 2007/08/13
- Re: --no-parser options, tim, 2007/08/14