1. 18 Mar, 2012 2 commits
  2. 25 Jan, 2012 2 commits
    • François Bobot's avatar
      Session doesn't use anymore prover id. · 2e2e0d83
      François Bobot authored
      Prover ids are only used for the command line option "-P".
      The user can choose what he wants (they must be unique)
      The prover name and version should not be modified. If someone want to
      test different command line options for a prover he can use the
      "alternative" field.
      
      If someone want to replay an external proof but he doesn't have the
      corresponding prover (same name,version,alternative), why3ide ask for
      a replacement among the known provers. The choice can be saved.
      2e2e0d83
    • François Bobot's avatar
      ac98a7a4
  3. 15 Dec, 2011 1 commit
    • Guillaume Melquiond's avatar
      Add an --extra-config option to load additional configuration. · 5c4b2517
      Guillaume Melquiond authored
      The loaded files are slimmed down version of the standard configuration
      file. They only support the following sections and fields:
      
      [main]
        loadpath=
        plugin=
      [prover ...]
        option=
        driver=
      
      It is also possible to define brand new [prover] sections.
      
      For now, the only supported frontends are why3 and why3ide.
      5c4b2517
  4. 04 Nov, 2011 1 commit
  5. 24 Sep, 2011 1 commit
    • Guillaume Melquiond's avatar
      Keep track of "ITP" provers and avoid running such provers on unedited proofs. · 406f058e
      Guillaume Melquiond authored
      When the user wants to write a Coq proof, she needs to run Coq on the goal,
      wait five seconds for it to fail (it will fail, otherwise there is no point
      in running Coq on this goal: another prover would have succeeded already),
      and finally edit it. This is a waste of time. So goals run with an
      interactive prover are now marked as unknown until their file is edited.
      
      Interactive provers could have been detected by a nonempty "editor" string,
      but there are interactive provers that don't have dedicated editors, and
      there might be automated provers with dedicated user interfaces. So a new
      field was added to prover descriptions.
      
      TODO: actually run the editor when there is only one selected goal,
      rather than keeping the current three-click method of editing proofs.
      406f058e
  6. 01 Jul, 2011 1 commit
  7. 24 May, 2011 1 commit
  8. 22 Apr, 2011 1 commit
    • François Bobot's avatar
      autodetection : simplify the semantics of the file provers-detection-data.conf · ef43f13a
      François Bobot authored
      * all the provers with the same prover_id are threated as one prover,
      * the first description of a prover in the file pdd.conf which have an
        executable with a good version is used,
      * the order used to test the executable (exec) inside a prover description
        is not specified,
      * a version_bad allows to forbid a version.
      * a version_ok matches no warning is printed
      * a version_old matches a warning is printed
      * if no version matches a warning is printed
      ef43f13a
  9. 31 Mar, 2011 1 commit
  10. 20 Feb, 2011 1 commit
  11. 19 Feb, 2011 1 commit
  12. 15 Feb, 2011 1 commit
  13. 13 Dec, 2010 1 commit
  14. 12 Nov, 2010 1 commit
  15. 26 Oct, 2010 1 commit
  16. 25 Oct, 2010 1 commit
  17. 08 Sep, 2010 1 commit
  18. 04 Sep, 2010 2 commits