[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bison-2.4.1 with more graph output
From: |
Joel E. Denny |
Subject: |
Re: bison-2.4.1 with more graph output |
Date: |
Wed, 17 Mar 2010 15:34:35 -0400 (EDT) |
User-agent: |
Alpine 1.00 (DEB 882 2007-12-20) |
Hi Akim, Tys,
On Wed, 17 Mar 2010, Akim Demaille wrote:
> > It is easy to add the older vcg driver in bison source,
> > and does not need maintance, it is bugfree and friendly
> > to offer users a choice of output graph type,
> > and no hidden 'vendor lock-in' to non-GPL software.
>
> Yes, but I'm no big fan of having several outputs here. Joel might have
> another opinion. Maybe gnulib could support a factored means to support
> both outputs. But the xsl-based approach you recently proposed seems a
> more acceptable path.
We plan for the XML output to be a stable user-visible interface to the
parser tables, so XSLT should be easier to maintain than internal Bison
code to support VCG.
More generally, I see no reason to reject any decent XSLT contribution
that might be useful to Bison users. Maybe there should be some sort of
data/xslt/contrib for XSLT that is not considered part of the core Bison
feature set. For any contributed XSLT, there must be test cases to make
sure we don't break it as the XML output evolves. Maybe
tests/xslt-contrib.at.
bison and gccgo go language, tys lefering, 2010/03/11