traces: don't print the stack before the gotos

The C, C++ and D skeletons used to show the stack right after popping
the stack during the reduction.  Now that the stack is printed after
reaching a new state, that has become useless:

    Entering state 1
    Stack now 0 1
    Reducing stack by rule 5 (line 83):
       $1 = token "number" (1)
    -> $$ = nterm exp (1)
    Stack now 0
    Entering state 8
    Stack now 0 8

Remove the "Stack now 0" line.

* data/skeletons/lalr1.cc, data/skeletons/lalr1.d,
* data/skeletons/lalr1.java, data/skeletons/yacc.c:
Here.
This commit is contained in:
Akim Demaille
2020-02-05 07:26:42 +01:00
parent 37aeda6fb3
commit d727e0ff23
8 changed files with 1 additions and 16 deletions

View File

@@ -658,14 +658,12 @@ Reducing stack by rule 1 (line 34):
$1 = token NUMBER (1)
-> $$ = nterm expr (10)
destroy: 1
Stack now 0
Entering state 2
Stack now 0 2
Reading a token
Next token is token NUMBER (30)
Reducing stack by rule 2 (line 35):
-> $$ = nterm @1 (20)
Stack now 0 2
Entering state 4
Stack now 0 2 4
Next token is token NUMBER (30)
@@ -681,7 +679,6 @@ expr: 10 20 30
destroy: 30
destroy: 20
destroy: 10
Stack now 0
Entering state 2
Stack now 0 2
Reading a token