Closed sykloid closed 6 years ago
Hi,
We support backward compatibility with APRON at the moment, allowing analyzers written with APRON to benefit from ELINA's faster algorithm. However, the plan going forward is to slowly deprecate support for APRON, so binding with ELINA may be more preferable. Let me know if there are any issues with ELINA.
Cheers, Gagan
Thanks for the quick response!
I'll consider going straight toward binding ELINA then.
That said, is it reasonable to use Apron's API documentation (http://apron.cri.ensmp.fr/library/0.9.10/apron.pdf) as a starting point to understanding ELINA's architecture in its current state? E.g. to answer questions such as: "Is elina_abstract0_t
the appropriate entry-point to ELINA operations?"
Hi,
Yes, ELINA API is compatible with APRON and thus "elina_abstract0_t" has the same semantics as "ap_abstract0_t" currently.
Cheers, Gagan
Thanks. I'll close this ticket for now, since I've decided to bind ELINA directly. I'll create other tickets for more specific questions.
Haskell bindings for a static analysis framework such as ELINA or apron would be great! Is anybody aware of going activities in that direction?
I'm in the process of writing Haskell bindings for ELINA, and having found Apron, I'm considering going through it instead for consistency.
What is the status of ELINA's Apron support? Is it a preferable way forward for implementing language bindings, or should I be binding ELINA directly?
Thanks!