[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bison version in graph output file

From: tys lefering
Subject: Re: bison version in graph output file
Date: Sun, 2 May 2010 01:32:18 +0200
User-agent: SquirrelMail/1.4.18

On Sat, May 1, 2010 02:02, Joel E. Denny wrote:
> Graphviz also supports comments starting with "//", so what do you think
> of the first patch below?
use of c++ comment style to prevent trouble with possible
unusual filenames looks good idea and should not be any
problem for tools reading dot graphs.

actually liked the use of 'digraph "parser-name" { }'
because it is usefull and maybe better then 'Automation'.

for example can put this way graph title in window top
in vcgview which is a gtk+ gui tool reading dot graph.

also the graph title will appear in few types of dot
output, for example the ps output with 'dot -Tps' as:

%%Creator: graphviz version 2.26.3 (20100126.1600)
%%Title: title-of-the-dot-graph

when using 'digraph "title-of-the-dot-graph" { ... }'

do not know how a GNU GPL kde tool for viewing dot graphs
is using the graph title somewhere. (it is unmaintained?)

there may be more tools which use a graph title,
if possible would be nice if it can be more then
only the fixed bison default of 'Automation'.

for grep it can be idea to put bison version string
and parser name in one line, then 'grep bison *.dot'
does show the bison graphs and what it is about in
a directory with many different dot graph files.

noticed there is no statement about the copyright status
of gcc and bison generated graph output files, assuming
it is "undefined" and maybe not good situation for the
fsf free software foundation.

> The second patch brings xml2dot.xsl up to date so that
> maintainer-xml-check passes.

Thanks for your attention on these details of bison graph output.


"all of the giant planets in our solar
system have methane too, despite their
lack of cows." (on slashdot)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]