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

displayname of Taclets need to be free of spaces. #3286

Closed
wadoon opened this issue Sep 27, 2023 · 0 comments · Fixed by #3306
Closed

displayname of Taclets need to be free of spaces. #3286

wadoon opened this issue Sep 27, 2023 · 0 comments · Fixed by #3306

Comments

@wadoon
Copy link
Member

wadoon commented Sep 27, 2023

Description

A proof can not be reloaded by KeY if a Taclet was used which (a) contains spaces in the \displayname meta-information and (b) has user-defined variable.

In the background, KeY writes a term definition in the proof file containing an origin clause using the \displayname. This term definition, especially, the origin label definition is wrong and leads to an exception.

Reproducible

Is the issue reproducible?

always

Steps to reproduce

Describe the steps needed to reproduce the issue.

  1. Define a (or modify) taclet to have a \displayname with spaces.
    test_assume { \schemavar formula phi; \add(phi ==>); \displayname "Test Test" }; 
    
  2. Use the taclet in a proof.
  3. Store and reload the proof.
  4. Observe an exception like this:
(Well-formed origins have one of the following formats: "spec_type @ file <file name> @ line <line number>")
spec_type @ node <node number> (<rule name>)")
spec_type (implicit)")
@wadoon wadoon changed the title displayname of Taclets need to free of spaces. displayname of Taclets need to be free of spaces. Sep 27, 2023
@wadoon wadoon mentioned this issue Sep 28, 2023
2 tasks
unp1 added a commit that referenced this issue Oct 19, 2023
@unp1 unp1 self-assigned this Oct 19, 2023
unp1 added a commit that referenced this issue Oct 19, 2023
github-merge-queue bot pushed a commit that referenced this issue Oct 19, 2023
unp1 added a commit that referenced this issue Oct 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants