Une MAJ de sécurité est nécessaire sur notre version actuelle. Elle sera effectuée lundi 02/08 entre 12h30 et 13h. L'interruption de service devrait durer quelques minutes (probablement moins de 5 minutes).

  1. 13 May, 2014 1 commit
  2. 23 Apr, 2014 1 commit
  3. 30 Mar, 2014 2 commits
    • MARCHE Claude's avatar
      5cae7968
    • Jean-Christophe Filliâtre's avatar
      new tool why3wc · c365d67b
      Jean-Christophe Filliâtre authored
      counts lines/tokens in Why3 files
      distinguishes spec (logic declarations and annotations) and code
      reports the ratio spec/code with command line option -f
      
      example: why3wc -f examples/*.mlw
      see why3wc --help for more details
      
      note: why3wc assumes that input files are lexically well-formed
      it also makes some approximations (switching from spec to code and
      conversely is only done when there is a blank line in the middle)
      c365d67b
  4. 21 Mar, 2014 2 commits
  5. 19 Mar, 2014 6 commits
  6. 18 Mar, 2014 2 commits
  7. 14 Mar, 2014 2 commits
  8. 06 Mar, 2014 1 commit
  9. 05 Mar, 2014 1 commit
  10. 04 Mar, 2014 1 commit
  11. 28 Feb, 2014 1 commit
  12. 27 Feb, 2014 1 commit
  13. 26 Feb, 2014 1 commit
  14. 25 Feb, 2014 1 commit
  15. 24 Feb, 2014 1 commit
  16. 21 Feb, 2014 1 commit
  17. 17 Feb, 2014 1 commit
  18. 16 Feb, 2014 3 commits
  19. 15 Feb, 2014 4 commits
  20. 14 Feb, 2014 1 commit
  21. 07 Feb, 2014 1 commit
  22. 01 Feb, 2014 1 commit
  23. 28 Jan, 2014 1 commit
  24. 27 Jan, 2014 1 commit
  25. 21 Jan, 2014 1 commit
  26. 20 Jan, 2014 1 commit
    • Andrei Paskevich's avatar
      "eliminate_epsilon" added in drivers · 9c20cd7c
      Andrei Paskevich authored
      Currently, the builtin theory why3.HighOrd (or just HighOrd) must
      be explicitly "use"-d. However, the type (HighOrd.func 'a 'b) can
      be written ('a -> 'b), and the type (HighOrd.pred 'a) can be written
      ('a -> bool), and the application operation (HighOrd.(@)) can be
      written as the usual juxtaposition. Thus, normally, you do not have
      to write the qualifiers. The builtin theory why3.Bool (or just Bool)
      is needed for "bool". The names "HighOrd", "func", "pred", and "(@)"
      are not yet fixed and may change.
      
      "eliminate_epsilon" tries to be smart when a lambda (or some other
      comprehension form) occurs under equality or at the top of a definition.
      We could go even further and replace (\ x . t) s with t[x <- s], without
      lifting the lambda. I'm not sure it's worth it: we rarely write redexes
      manually. They can and will appear through inlining, though.
      
      Anyone who wants to construct epsilon-terms directly using the API
      should remember that these are not Hilbert's epsilons: by writing
      an epsilon term, you postulate the existence (though not necessarily
      uniqueness) of the described object, and "eliminate_epsilon" will
      happily convert it to an axiom expressing this existence. We only
      use epsilons to write comprehensions whose soundness is guaranteed
      by a background theory, e.g. lambda-calculus.
      9c20cd7c