1. 25 Jul, 2012 2 commits
  2. 23 Jul, 2012 5 commits
    • François Bobot's avatar
    • François Bobot's avatar
      prover identification: use shortcuts · 92165a83
      François Bobot authored
         shortcuts are defined in why3.conf. They are automatically
         generated using two mechanism:
         - a shortcut section in prover-detection-data.conf creates a shortcut
         for the first prover that match the regexp
         - the identifier used as family argument for the prover section in
         prover-detection-data.conf is used as shortcut for the prover. If
         different sections use the same argument the first one that match an
         existing prover is used for the shortcut.
    • François Bobot's avatar
      new prover identification: remove id · 5a3641ec
      François Bobot authored
             Remove the id in prover that is used only for command-line, use
             instead the name,version,alternative of the prover. One can
             also use regular expression (start with ^).
             "Alt-Ergo,0.92,with arrays" corresponds only to one prover
             "Alt-Ergo,^0\.9.*,with arrays" correspond to all the Alt-Ergo prover with arrays which version match "0\.9.*"
             "Alt-Ergo" is the same thing than "Alt-Ergo,^,^"
             "Alt-Ergo,0.92," corresponds only to one prover with the alternate fields empty
             "Alt-Ergo,,with arrays" corresponds to "Alt-Ergo,^,with arrays" since the version is never empty.
             Provers identification are case sensitive even if it is
             currently more complicated for the user because
             case-insensitiveness is not sufficient. Specifiying "alt-ergo"
             for "Alt-Ergo,^,^" is great, but not if there is more than one
             match. A more general system of shortcut would be more
    • François Bobot's avatar
      extraconfig: fix · 043a5bcd
      François Bobot authored
    • François Bobot's avatar
  3. 20 Jul, 2012 1 commit
  4. 20 May, 2012 1 commit
  5. 16 Apr, 2012 1 commit
  6. 15 Apr, 2012 1 commit
  7. 12 Apr, 2012 2 commits
  8. 09 Apr, 2012 2 commits
  9. 18 Mar, 2012 1 commit
  10. 31 Jan, 2012 1 commit
    • François Bobot's avatar
      Why3session : a new why3 program · da5b5d18
      François Bobot authored
      It's goal is to allow to view and modify sessions.
      Currently three sub-commands :
      info : can give the provers used, pretty-print in ascii a session,
           can give the corresponding directory
      mod : allow to set obsolete, or modify the archive state of proof attempt
          which corresponds to selected provers
      copy : copy a proof attempt by modifing its prover
  11. 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.
    • François Bobot's avatar
  12. 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:
      [prover ...]
      It is also possible to define brand new [prover] sections.
      For now, the only supported frontends are why3 and why3ide.
  13. 13 Dec, 2011 1 commit
  14. 28 Nov, 2011 1 commit
  15. 24 Nov, 2011 1 commit
  16. 17 Nov, 2011 1 commit
  17. 09 Nov, 2011 1 commit
  18. 13 Oct, 2011 1 commit
  19. 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.
  20. 05 Jul, 2011 1 commit
  21. 02 Jul, 2011 2 commits
  22. 01 Jul, 2011 1 commit
  23. 24 May, 2011 1 commit
  24. 22 May, 2011 1 commit
  25. 21 Apr, 2011 2 commits
  26. 20 Feb, 2011 2 commits
  27. 19 Feb, 2011 1 commit
  28. 16 Feb, 2011 2 commits