-
Notifications
You must be signed in to change notification settings - Fork 17
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
Can't parse TIP v0.3 #88
Comments
Depending on how complicated the changes are, you might have an easier time just adapting the current parser to follow TIP 3. It's nice that they got closer to smtlib, I must say. I don't have any time to work on this personally, though. |
I've adapted the grammar and pushed it directly to The example |
Thank you very much for the swift responses and the quick implementation! Regarding issues, the following archive contains all the files from Furthermore, here is an archive of all the files that throw the same error you noticed with Once again, thank you for your help! |
I've fixed the parsing issue and pushed it to The A workaround would be to replace |
Apparently, the TIP language has incorporated SMT-LIB 2.6 changes (tip-org/tools@2995668) and is therefore no longer compatible with zipperposition's current parser:
Since BNFC claims to be able to output Menhir files and the lbnf file is available, I suppose it would be little effort to update the parser, although I don't know anything about menhir and the way its output is used in zipperposition (otherwise I would've made a quick PR myself). Do you think this is feasible?
To give a little background: I'd like to add TIP support to Hets (spechub/Hets#1502) to enable it to eventually talk to several induction-capable provers with relatively little translation effort of its own, using the TIP-provided tools instead. I plan on testing the implementation by connecting a prover that already talks TIP natively (e.g. zipperposition). Since the generated TIP should eventually be fed into TIP's (up-to-date) translator, I want to avoid implementing an old version of the language if possible.
The text was updated successfully, but these errors were encountered: