[Top][All Lists]

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

Re: RFC: Default output destination

From: Akim Demaille
Subject: Re: RFC: Default output destination
Date: 02 Oct 2000 18:51:37 +0200
User-agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands)

| On Mon, Oct 02, 2000 at 05:48:26PM +0200, Akim Demaille wrote:
| : (And BTW, why the heck is there this `tab' part?)
| I believe it is short for "table" - the compiler parser is based on using a
| state transition table or something along those lines.  That's my guess -
| I've never used lex/yacc seriously and am no expert in this field ;)


Actually I was referring to the fact that there this `.tab' part in
the name.  I find it ugly and unneeded, all we need is the
extensions.  It looks like remains of the old Yacc behavior that has
been only partly cleaned up.

If I were to design the interface today, bison FOO.y would create
plenty of FOO.ext files, not a mixture of and FOO.ext:

/tmp/src % ls                                                    nostromo 18:49
/tmp/src % bison --defines --verbose calc.y                      nostromo 18:49
/tmp/src % ls -l                                                 nostromo 18:49
total 43
-rw-r--r--    1 akim     lrde         9845 oct  2 18:49 calc.output
-rw-r--r--    1 akim     lrde        27469 oct  2 18:49
-rw-r--r--    1 akim     lrde          100 oct  2 18:49
-rw-r--r--    1 akim     lrde         3335 oct  2 16:31 calc.y

This is more like what I'm expecting from Bison:

/tmp/src % rm *~*y                                               nostromo 18:50
/tmp/src % bison --defines --verbose calc.y -o my-calc.c         nostromo 18:50
/tmp/src % ls                                                    nostromo 18:50
calc.y  my-calc.c  my-calc.h  my-calc.output


reply via email to

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