IllegalArgumentException in B Console for symbolic return values
Description
Environment
None
Activity
Show:
Michael Leuschel November 10, 2020 at 12:14 PM
get_error_messages now returns the empty list when there are no warnings and no errors, commit
0793c25bac7ec256ebe6af1992386989593c7aa9
There is, however, still the issue that if warnings occur during evaluation of an expression, we get the result string as first part of the error term, which would still lead to an illegal argument exception. Ideally, we should make the code in Java more robust and also extend it to include messages / warnings.
Michael Leuschel November 10, 2020 at 11:21 AM
This is possibly due to the fact that messages are now passed to ProB2; in b_interpreter.pl we have:
Fixed
Details
Details
Assignee
Unassigned
UnassignedReporter
Michael Leuschel
Michael LeuschelPriority
Created November 10, 2020 at 11:11 AM
Updated November 16, 2020 at 11:16 AM
Resolved November 16, 2020 at 11:16 AM
When typing the following into the B Console
{x|x:NATURAL & not(x:NAT)}
I get this exception: