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

Plato: Error Messages #1

Open
GoogleCodeExporter opened this issue May 2, 2015 · 2 comments
Open

Plato: Error Messages #1

GoogleCodeExporter opened this issue May 2, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

Plato doesn't yet accept error messages for constraints.

This is partly by design because when Plato combines constraints it would then
need to generate a new error message for the combination.

Implementationally, it is hard to do that because we're using Snark to compute 
the resolution closure.

Suggestion: attach error messages only to the original constraints.  For the 
case when the resolution closure is just the original theory, everything works 
out (which is always true for non-interacting constraints---a common case).  Or 
even more simply, just keep the error messages around for complete theories.

Syntactically, we can change the input language for constraints so that they 
are ...
(formula1 "explanation1"  formula2 "explanation2" ....)

Internally, perhaps we can just maintain a simple alist (formulai . 
"explanationi").  Then when we convert each formula to clausal form, we just 
replicate explanationi for each clause generated from formulai.  Finally, when 
doing the compilation we simply check if for an error message using sent-equal. 


Original issue reported on code.google.com by thinr...@gmail.com on 21 Jun 2012 at 3:06

@GoogleCodeExporter
Copy link
Author

Original comment by thinr...@gmail.com on 20 Sep 2012 at 6:14

  • Changed title: Plato Error Messages

@GoogleCodeExporter
Copy link
Author

Original comment by thinr...@gmail.com on 20 Sep 2012 at 6:14

  • Changed title: Plato: Error Messages

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

No branches or pull requests

1 participant