1. 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
      da5b5d18
  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. 27 Dec, 2011 1 commit
  4. 25 Oct, 2011 1 commit
  5. 30 Sep, 2011 2 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.
      9ab0704b
    • 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
      b92e64bc
  6. 29 Sep, 2011 1 commit
  7. 27 Sep, 2011 1 commit
  8. 17 Sep, 2011 1 commit
  9. 02 Jul, 2011 2 commits
  10. 01 Jul, 2011 2 commits
  11. 30 Jun, 2011 1 commit
  12. 18 Jun, 2011 1 commit
  13. 11 Jun, 2011 1 commit
    • Andrei Paskevich's avatar
      a little refactoring in Env · b8dcebfc
      Andrei Paskevich authored
      - create_env_of_loadpath is now provided in Env instead of Lexer
      - find_channel functions now depend on format to determine the
        suitable extensions
      b8dcebfc
  14. 24 May, 2011 1 commit
  15. 03 May, 2011 1 commit
  16. 16 Mar, 2011 1 commit
  17. 15 Mar, 2011 1 commit
  18. 20 Feb, 2011 1 commit
  19. 16 Feb, 2011 1 commit
  20. 15 Feb, 2011 1 commit
  21. 28 Jan, 2011 1 commit
  22. 27 Jan, 2011 1 commit
  23. 26 Dec, 2010 1 commit
  24. 18 Dec, 2010 1 commit
  25. 13 Dec, 2010 1 commit
  26. 10 Dec, 2010 1 commit
  27. 05 Dec, 2010 1 commit
  28. 01 Dec, 2010 2 commits
  29. 12 Nov, 2010 2 commits
  30. 29 Sep, 2010 1 commit
  31. 04 Sep, 2010 3 commits
  32. 02 Sep, 2010 1 commit