work around diagnostic changes in Bison 3.6

Bison <3.6 used to complain about "$undefined", while Bison >=3.6 now
write "invalid token".

* tests/core/parseaut.test, tests/core/parseerr.test,
tests/core/sugar.test: Adjust expected diagnostics to match Bison pre
and post 3.6.
This commit is contained in:
Alexandre Duret-Lutz 2020-05-24 14:05:46 +02:00
parent 16540869d4
commit e06f8a3ece
3 changed files with 18 additions and 14 deletions

View file

@ -1,7 +1,7 @@
#! /bin/sh
# -*- coding: utf-8 -*-
# Copyright (C) 2018, 2019 Laboratoire de Recherche et Développement
# de l'Epita (LRDE).
# Copyright (C) 2018-2020 Laboratoire de Recherche et Développement de
# l'Epita (LRDE).
#
# This file is part of Spot, a model checking library.
#
@ -135,11 +135,12 @@ EOF
num="number for square bracket operator"
numoreof="$num or end of formula"
sep="separator for square bracket operator"
undefined='$undefined'
undefined='invalid token'
closingbkt='square bracket operator, expecting closing bracket'
eclosingbkt='expecting closing bracket or closing !]'
ltlfilt -F err.in 2>err && exit 1
sed 's/[$]undefined/invalid token/' err >err2
cat >expect2 <<EOF
ltlfilt:err.in:1: parse error:
>>> F[
@ -329,4 +330,4 @@ syntax error, unexpected closing brace
missing right operand for "SVA delay operator"
EOF
diff -u err expect2
diff -u err2 expect2