Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

list of discrepancies between SBCL- and Allegro-PVS #97

Open
kai-e opened this issue Apr 3, 2023 · 0 comments
Open

list of discrepancies between SBCL- and Allegro-PVS #97

kai-e opened this issue Apr 3, 2023 · 0 comments

Comments

@kai-e
Copy link

kai-e commented Apr 3, 2023

  1. SBCL stores all proof commands in ALL CAPS; this confuses Allegro (sometimes)
  2. file-targetting proof commands (status-proof-pvs-file, prove-pvs-file, etc.) finish with a message such as

PVS file pythagoras.pvs not found

  1. Proof commands that interact with the user such as (undo), (quit), or the prompt whether one would like to save a proof when it's done, don't show up in the *pvs* buffer right away. Instead, for instance, after a proof was finished

Trying repeated skolemization, instantiation, and if-lifting,
Q.E.D.
^G

shows up. The prompt is not shown before something is entered (y in this case, and then no).

y
Would you like the proof to be saved? (yes or no)
Please type "yes" for yes or "no" for no.
no
Would you like the proof to be saved? (yes or no)

Run time = 0.18 secs.
Real time = 145.20 secs.
NIL
PVS(26):

  1. Times reported for proofs look wrong. They typically are, e.g.
little_known_pythagorean..............proved - complete   [SHOSTAK](0.00 s)

even when considerable time was spent running that proof.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant