Baier D.

Note: we will postpone this branch until we are up-to-date with Java21 to avoid problems and utilize BV and FP support in SMTInterpol.

I am very much in favor of 2. (Switch to Ultimate for building SMTInterpol), as there is another [branch](https://github.com/sosy-lab/java-smt/tree/add_solver_independent_quantifier_elimination_with_ultimate_eliminator) that will use/import Ultimate anyways!

Would that mean we need to switch to Java 21?

> I've added transparent escaping/unescapig with [a43cb6d](https://github.com/sosy-lab/java-smt/commit/a43cb6dc2528b851afdb0d2d759f3393dff46a3a). This means that all variables are now allowed, and the escaping is done automatically when needed. > > We still have to figure...

Sorry for the late reply! If it is beneficial just remove it from the wrapper. Since #427 is already merged, we can still use this in the most recent update...

[!492](https://github.com/sosy-lab/java-smt/issues/492) should be looked at first before continuing to see if it affects this PR.

> [!492](https://github.com/sosy-lab/java-smt/issues/492) should be looked at first before continuing to see if it affects this PR. Since the new version is merged, we should take a look if this issue...

Something that might be worth a try is adding a static `info()` method that tries to read your OS and gives you information about available solvers, dependencies and requirements (e.g....

Progress for OpenSMT2 + tests in branch [improve opensmt2 parsing](https://github.com/sosy-lab/java-smt/tree/improve_opensmt2_parsing)

Whats the current state of this issue and what can we do? @daniel-raffler could you investigate please?