Currently the C and C++ parse traces differ in the order in which the
stack is displayed: bottom up in C, top down in C++. Let's stick to
the C order.
* data/skeletons/stack.hh (stack::iterator, stack::const_iterator)
(begin, end): Be forward, not backward.
---
data/skeletons/lalr1.cc | 2 --
Make testing easier by reducing differences between skeletons.
Akim Demaille (4):
style: avoid redundancy in the tests
c++: display the stack in the same order as in C
c++: report the stack at the same places as in C
d, java: use traces more alike that of C
data/skeletons/lalr1.cc |
* tests/local.at (m4_rpatsubst): New.
Use it to handle %parse-params.
* tests/calc.at: Use %parse-params with several arguments.
---
tests/calc.at | 27 ++-
tests/local.at | 22 +++---
2 files changed, 33 insertions(+), 16 deletions(-)
diff --git
Let's have C be the reference, and match it elsewhere. Maybe C is too
verbose and some adjustments are needed, but then that would be done
in another batch of patches.
* data/skeletons/lalr1.cc: Print the stack once we popped after
YYERROR, and before emptying the stack at the end of parsing.
On Freitag, 10. Januar 2020 07:23:43 CET Akim Demaille wrote:
> Hi Christian!
Hi Akim,
> > Le 9 janv. 2020 à 14:50, Christian Schoenebeck
> > a écrit :>
> > On Sonntag, 5. Januar 2020 17:52:43 CET Akim Demaille wrote:
> >>> Why not making that a general-purpose function instead that users
Hi Jannick,
> Le 13 janv. 2020 à 08:18, Jannick a écrit :
>
> Hi Akim,
>
> looking into travis a bit, here something which might be easier (locally I
> am working along the following lines as well):
> - use the MSYS2 shell
>
Hi Christian,
Thanks for your answer! I definitely need feedback on these matters.
> Le 14 janv. 2020 à 14:50, Christian Schoenebeck a
> écrit :
>
>> I wouldn't call memory management in yacc.c "easy": lots of efforts
>> are made to allocate on the call stack, and to avoid malloc.
>
> For
