1. 03 Aug, 2012 1 commit
    • François Bobot's avatar
      Documentation: add description to all the registration functions · 29201f7c
      François Bobot authored
       (metas, debug flags, transformations, formats) except for label.
      
      This description is used in --list-*. The description can use any of
      the formatting markup of Format "@ " "@[",...
      
      Transformations can also specify from which metas and labels they
      depend, and add informations about how they are interpreted.
      
      TODO:
        - complete and correct the documentation
        - when a transformation use Trans.on_meta, it should be possible to
          add an interpretation of the metas in the documentation.
        - recover a summary version of --list-* ?
        - be able to export in latex?
      29201f7c
  2. 28 Jul, 2012 1 commit
  3. 24 Jul, 2012 1 commit
  4. 18 Jul, 2012 1 commit
  5. 14 Jul, 2012 1 commit
  6. 28 Jun, 2012 2 commits
    • Andrei Paskevich's avatar
      whyml: include pure symbols in the program namespace · 55c1fc02
      Andrei Paskevich authored
      Thus, we do not need to look through two different namespaces.
      The only difference w.r.t. the core namespace semantics is that
      a program symbol (pvsymbol, psymbol, plsymbol, or xsymbol) may
      be introduced in the scope of an lsymbol of the same name and
      overshadow it in program expressions, though not in specifications.
      For example, the following declarations allow to use (!) both in
      programs and specifications:
      
          type ref 'a = {| mutable contents : 'a |}
          function (!) (x: ref 'a) : 'a = x.contents
          let (!) (r: ref 'a) = {} r.contents { result = !r }
      
      Notice, however, that itsymbols cannot overshadow pure tsymbols.
      55c1fc02
    • Andrei Paskevich's avatar
      a384381e
  7. 17 Jun, 2012 1 commit
  8. 07 Jun, 2012 1 commit
  9. 26 May, 2012 1 commit
  10. 22 May, 2012 1 commit
  11. 15 May, 2012 1 commit
  12. 07 May, 2012 1 commit
  13. 06 May, 2012 1 commit
  14. 09 Apr, 2012 1 commit
  15. 18 Mar, 2012 3 commits
  16. 29 Feb, 2012 1 commit
  17. 26 Feb, 2012 1 commit
  18. 22 Feb, 2012 1 commit
    • Andrei Paskevich's avatar
      make api of maps/sets more consistent · 33bb423f
      Andrei Paskevich authored
      - change takes function as the first argument
      - add_new takes exception as the first argument
      - find_default is renamed to find_def and takes the default value
        as the first argument
      - find_option is renamed to find_opt (to align with find_exn and find_def)
      - default_option is renamed def_option
      33bb423f
  19. 21 Feb, 2012 2 commits
  20. 19 Feb, 2012 1 commit
  21. 14 Feb, 2012 1 commit
  22. 10 Feb, 2012 1 commit
  23. 09 Feb, 2012 1 commit
  24. 08 Feb, 2012 3 commits
  25. 06 Feb, 2012 1 commit
  26. 03 Jan, 2012 1 commit
    • François Bobot's avatar
      new session · 49c19a38
      François Bobot authored
      Split session in two :
      Session : an API for managing session without running provers
      Session_scheduler : an API for running provers asynchronously
      
      All the global states have been removed.
      
      A session must be first read, which give a session without task.
      Afterward it must be updated to the current state of the files with
      some environnement and configuration.
      
      printer and iterator are provided for session.
      
      Session_tools : some useful functions on session.
      
      Smoke detector : not anymore integrated to session. Just add the
            transformation "smoke_detector_top" or "smoke_detector_deep" to
            all the valid proof attempt.
      
      prover_id are not yet removed but all is in place in session for that.
      49c19a38
  27. 20 Dec, 2011 1 commit
    • Guillaume Melquiond's avatar
      Move Coq realizations from a .ml file to a driver file. · cc79baa8
      Guillaume Melquiond authored
      Note that the file is still generated at compilation time.
      
      The "realized" meta takes two arguments. The first one is the path+name of
      the theory, the second one is the translation of it for the target prover.
      The meta is supposed to be put into a printer file, so there is no
      ambiguity on the target. The second argument can be left empty if it can be
      inferred from the first one.
      
      Note that the first argument is not really satisfactory, since it is
      redundant with the theory part of the driver. Moreover, its handling is a
      bit crude: it does not take into account rich qualifiers and it does not
      generate proper error messages if it does not match the theory.
      cc79baa8
  28. 16 Nov, 2011 1 commit
  29. 30 Sep, 2011 1 commit
  30. 29 Sep, 2011 3 commits
  31. 28 Sep, 2011 2 commits