ID0002484: **This issue was created automatically from Mantis Issue 2484. Further discussion may take place here.** --- | **Id** | **Project** | **Category** | **View** | **Due Date** | **Updated** | | --- | --- | --- | --- | --- | --- | | ID0002484 | Frama-C | Plug-in > wp | public | 2019-11-08 | 2019-11-08 | | | | | | | | | --- | --- | --- | --- | --- | --- | | **Reporter** | jens | **Assigned To** | correnson | **Resolution** | open | | **Priority** | normal | **Severity** | minor | **Reproducibility** | have not tried | | **Platform** | Linux | **OS** | xubuntu | **OS Version** | - | | **Product Version** | Frama-C GIT, precise the release id | **Target Version** | - | **Fixed in Version** | - | ### Description : This is a hint to (better) describe the transition from using alt-ergo in Frama-C 19 and 20. If it is already described, then I apologize. In Frama-C 19 and before one uses -wp-prover alt-ergo for the native interface and -wp-prover why3:alt-ergo for the Why3 interface In Frama-C 20 the respective options are -wp-prover native:alt-ergo for the native interface and -wp-prover alt-ergo I propose that it is described with other things in a short transition document.