1. 21 Mar, 2017 1 commit
  2. 20 May, 2016 1 commit
  3. 20 Apr, 2016 1 commit
  4. 24 Mar, 2016 2 commits
  5. 15 Mar, 2016 2 commits
  6. 18 Nov, 2015 1 commit
  7. 09 Sep, 2015 2 commits
  8. 21 Mar, 2015 3 commits
  9. 20 Mar, 2015 1 commit
  10. 19 Mar, 2015 1 commit
  11. 07 Nov, 2014 1 commit
  12. 14 Mar, 2014 1 commit
  13. 28 Nov, 2013 1 commit
  14. 22 Oct, 2013 1 commit
  15. 06 Mar, 2013 1 commit
  16. 30 Oct, 2012 1 commit
  17. 29 Oct, 2012 2 commits
  18. 21 Oct, 2012 5 commits
  19. 20 Oct, 2012 1 commit
    • Andrei Paskevich's avatar
      simplify copyright headers · 11598d2b
      Andrei Paskevich authored
      + create AUTHORS file
      + fix the linking exception in LICENSE
      + update the "About" in IDE
      + remove the trailing whitespace
      + inflate my scores at Ohloh
      11598d2b
  20. 18 Sep, 2012 1 commit
  21. 11 Sep, 2012 1 commit
  22. 08 Sep, 2012 1 commit
  23. 04 Aug, 2012 1 commit
  24. 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
  25. 25 Jul, 2012 1 commit
  26. 23 Jul, 2012 5 commits
    • François Bobot's avatar
    • François Bobot's avatar
      prover identification: use shortcuts · 92165a83
      François Bobot authored
         shortcuts are defined in why3.conf. They are automatically
         generated using two mechanism:
         - a shortcut section in prover-detection-data.conf creates a shortcut
         for the first prover that match the regexp
      
         - the identifier used as family argument for the prover section in
         prover-detection-data.conf is used as shortcut for the prover. If
         different sections use the same argument the first one that match an
         existing prover is used for the shortcut.
      92165a83
    • 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
    • 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