neverpase: fix parsing of neverclaim produced by ltl2ba and ltl3ba
These translator may output guards such as (a) || (b), but with the changes in Spot 1.1.3 it would only work with ((a) || (b)). Furthermore when ltlcross would fail to parse a neverclaim containing such a guard, it would fail to parse all later neverclaims, because the lexer was not properly reset. * src/neverparse/neverclaimscan.ll: Scan (a) || (b) as a single token. (neverclaimyyopen): Reset the lexer. * src/tgbatest/neverclaimread.test: Add a test for (a) || (b). * NEWS: Update.
This commit is contained in:
parent
365d0ead94
commit
84c9f03767
3 changed files with 45 additions and 1 deletions
7
NEWS
7
NEWS
|
|
@ -1,6 +1,11 @@
|
|||
New in spot 1.1.3a (not released)
|
||||
|
||||
* Nothing yet.
|
||||
* Bug fixes:
|
||||
- The parser for neverclaim, updated in 1.1.3, would fail to
|
||||
parse guards of the form (a) || (b) output by ltl2ba or
|
||||
ltl3ba, and would only understand ((a) || (b)).
|
||||
- When used from ltlcross, the same parser would fail to
|
||||
parser further neverclaims after the first failure.
|
||||
|
||||
New in spot 1.1.3 (2013-07-09)
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue