1. 07 Oct, 2011 2 commits
  2. 06 Oct, 2011 1 commit
  3. 05 Oct, 2011 1 commit
  4. 03 Oct, 2011 6 commits
  5. 01 Oct, 2011 1 commit
  6. 30 Sep, 2011 4 commits
    • Andrei Paskevich's avatar
      add the option --realize to Main · 9ab0704b
      Andrei Paskevich authored
      How to use it:
          why3 --realize -D drivers/coq-realize.drv -T real.Real -o .
              produces Real.v in the current directory
          why3 --realize -D drivers/coq-realize.drv -T real.Real
              produces real/Real.v in the loadpath near real.why
              (the directory "real" must exist)
      If a realization file is already there, it is passed to
      the printer in order to preserve the proofs.
      Instead of -D <driver_file>, you can use -P <prover>,
      if that prover uses a corresponding driver. However,
      the prover itself is not used.
      You can only realize theories from the loadpath.
      At the moment, coq-realize.drv is the only driver
      capable to realize theories in some sensible way.
      For any other driver, the results may be funny.
      Realization of WhyML modules is not possible so far.
      Realization may break if you directories and filenames
      contain non-alphanumeric symbols.
      The whole thing is in very preliminary stage.
      Use with caution.
    • Andrei Paskevich's avatar
    • Andrei Paskevich's avatar
      rename Env.create_env_of_loadpath to Env.create_env · b92e64bc
      Andrei Paskevich authored
      also add Env.get_loadpath to use for Coq realisation
    • MARCHE Claude's avatar
      alternative timeout regexp for vampire · 75e1e522
      MARCHE Claude authored
  7. 29 Sep, 2011 7 commits
  8. 28 Sep, 2011 7 commits
  9. 27 Sep, 2011 2 commits
  10. 26 Sep, 2011 7 commits
  11. 25 Sep, 2011 1 commit
  12. 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.