1. 21 Jan, 2013 2 commits
  2. 28 Nov, 2012 1 commit
  3. 13 Nov, 2012 1 commit
  4. 09 Nov, 2012 1 commit
  5. 08 Nov, 2012 1 commit
  6. 06 Nov, 2012 1 commit
  7. 30 Oct, 2012 3 commits
  8. 29 Oct, 2012 1 commit
  9. 21 Oct, 2012 8 commits
  10. 20 Oct, 2012 2 commits
  11. 02 Oct, 2012 1 commit
  12. 11 Sep, 2012 1 commit
  13. 08 Sep, 2012 1 commit
  14. 05 Sep, 2012 1 commit
  15. 04 Sep, 2012 1 commit
  16. 20 Aug, 2012 2 commits
    • François Bobot's avatar
      session: metas can be added · 3e20cfe5
      François Bobot authored
        - the symbols that appear in the metas are identified in the xml by
          their position in the task:
          - in which declaration
          - in which definition (if that apply otherwise -1)
          - in which constructor(or case in inductive predicate) (if that apply otherwise -1)
          - in which field (if that apply otherwise -1)
      
        - the md5sum of the prefix of the task that end with the declaration is used to know if the
          symbol have been changed, and if it is obsolete.
      
        - currently metas that contains obsolete symbol are removed.
      3e20cfe5
    • François Bobot's avatar
      stdlib: remove polymorphic hashtbl · 068ddc7b
      François Bobot authored
         - add functions to Hashtbl.S
         - without ocaml 3.12 its not possible to do that for Hashtbl without
           copying the signature
         - "open Stdlib" hides the polymorphic hashtbl, perhaps a good idea
           since that avoid errors.
      068ddc7b
  17. 04 Aug, 2012 2 commits
  18. 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
  19. 25 Jul, 2012 1 commit
  20. 24 Jul, 2012 1 commit
  21. 23 Jul, 2012 2 commits
    • 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
             appropriate.
      5a3641ec
    • François Bobot's avatar
      Autodetection: new semantic of provers-detection-data.conf · 48685ba9
      François Bobot authored
      Don't use anymore the family argument.
      
      1) For every block, for every executable call the prover using the
      version switch and add the prover to the configuration if the version
      match one of the version_ok or version_old but none of the version_bad
      2) We consider that an executable name which appears in a block, but
      which version isn't a version_ok, version_old or version_bad has an
      unknown version
      3) For every executable which have an unknown version, we add the
      prover using the first block that contains it.
      
      So the order of the block is used only when the version of an
      executable appears in none of the block.
      
      A block with more than one exec fields is now the same thing than if
      you split the block into blocks containing one field.
      
      New message field that allows to print a message when a prover is
      detected. If a message is not present, we print ", Ok." if the version
      is good (version_good) and not old, and " (it is an old version)." if
      the version is old (version_old).
      
      The field command can be missing in a block, in that case the block
      defines a version known to be buggy: no prover config is generated.
      48685ba9
  22. 16 Jul, 2012 1 commit
  23. 08 Jul, 2012 1 commit
  24. 29 Jun, 2012 1 commit
  25. 15 May, 2012 1 commit
  26. 06 May, 2012 1 commit