Re: bison info doc - precedence in recursive parsing
> On 5 Feb 2019, at 07:18, Akim Demaille wrote: > >> Le 4 févr. 2019 à 23:50, Hans Åberg a écrit : >> >>> On 4 Feb 2019, at 22:59, Uxio Prego wrote: >>> >>> can’t remember any such graphviz failure, even with graphs >>> so large, their output isn't actually useful, unless for navigating >>> with e.g. xdot. >>> >>> I however have only used -Tpng, never -Tpdf. Also no -O, but I >>> guess that’s simply and works the same for all cases. >> >> It didn't help with PNG, despite running for more than half an hour. >> Probably too big. > > Yes, on "real life grammars", Dot fails to render anything. And the result > would probably be useless anyway. This feature is very handy for small > grammars, but when it gets too big, you'd better look at the HTML report (or > text). It only generates XML, it seems: for HTML, using xsltproc, a style sheet is required, and Bison does not seem to come with that. ___ help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
Re: bison info doc - precedence in recursive parsing
> Le 5 févr. 2019 à 10:28, Hans Åberg a écrit : > > >> On 5 Feb 2019, at 07:18, Akim Demaille wrote: >> >> Yes, on "real life grammars", Dot fails to render anything. And the result >> would probably be useless anyway. This feature is very handy for small >> grammars, but when it gets too big, you'd better look at the HTML report (or >> text). > > It only generates XML, it seems: for HTML, using xsltproc, a style sheet is > required, and Bison does not seem to come with that. Yes it does. Have a look at the Makefiles of the examples. For instance, that of lexcalc. # This Makefile is designed to be simple and readable. It does not # aim at portability. It requires GNU Make. BASE = lexcalc BISON = bison FLEX = flex XSLTPROC = xsltproc all: $(BASE) %.c %.h %.xml %.gv: %.y $(BISON) $(BISONFLAGS) --defines --xml --graph=$*.gv -o $*.c $< %.c: %.l $(FLEX) $(FLEXFLAGS) -o$@ $< scan.o: parse.h lexcalc: parse.o scan.o $(CC) $(CFLAGS) -o $@ $^ run: $(BASE) @echo "Type arithmetic expressions. Quit with ctrl-d." ./$< html: parse.html %.html: %.xml $(XSLTPROC) $(XSLTPROCFLAGS) -o $@ $$($(BISON) --print-datadir)/xslt/xml2xhtml.xsl $< CLEANFILES =\ $(BASE) *.o \ parse.[ch] parse.output parse.xml parse.html parse.gv \ scan.c clean: rm -f $(CLEANFILES) ___ help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
Re: bison info doc - precedence in recursive parsing
> On 5 Feb 2019, at 18:56, Akim Demaille wrote: > >> Le 5 févr. 2019 à 10:28, Hans Åberg a écrit : >> >>> On 5 Feb 2019, at 07:18, Akim Demaille wrote: >>> >>> Yes, on "real life grammars", Dot fails to render anything. And the result >>> would probably be useless anyway. This feature is very handy for small >>> grammars, but when it gets too big, you'd better look at the HTML report >>> (or text). >> >> It only generates XML, it seems: for HTML, using xsltproc, a style sheet is >> required, and Bison does not seem to come with that. > > Yes it does. Have a look at the Makefiles of the examples. For instance, > that of lexcalc. Ah, I only looked at calc++ and the manual. It worked with my rather large grammar. ___ help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
