1. 11 Oct, 2011 2 commits
  2. 08 Oct, 2011 2 commits
  3. 07 Oct, 2011 11 commits
  4. 06 Oct, 2011 1 commit
  5. 05 Oct, 2011 1 commit
  6. 03 Oct, 2011 6 commits
  7. 01 Oct, 2011 1 commit
  8. 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
  9. 29 Sep, 2011 7 commits
  10. 28 Sep, 2011 5 commits