1. 21 Jan, 2013 1 commit
  2. 08 Nov, 2012 1 commit
  3. 21 Oct, 2012 2 commits
  4. 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
  5. 05 Aug, 2012 3 commits
  6. 04 Aug, 2012 1 commit
    • Andrei Paskevich's avatar
      make the meta_desc field immutable · 5ae69cd3
      Andrei Paskevich authored
      Provers will have native polymorphism support long before people will
      start writing third-party polymorphism encoding procedures for Why3.
      (And it's not that I have high hopes about the former.)
      5ae69cd3
  7. 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
  8. 14 Jul, 2012 1 commit
  9. 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
  10. 22 May, 2012 1 commit
  11. 09 Apr, 2012 1 commit
  12. 18 Mar, 2012 1 commit
    • Andrei Paskevich's avatar
      separate abstract types and logic symbols · 1b769a78
      Andrei Paskevich authored
      - put abstract types and aliases in Dtype of tysymbol
      - put (recursive) algebraic types in Ddata of (ts,constr list) list
      - put abstract function/predicate symbols in Dparam of lsymbol
      - put defined logic symbols in Dlogic of (ls,ls_definition) list
      1b769a78
  13. 21 Feb, 2012 1 commit
  14. 14 Feb, 2012 1 commit
  15. 28 Sep, 2011 1 commit
  16. 27 Sep, 2011 1 commit
  17. 01 Jul, 2011 1 commit
  18. 18 Jun, 2011 1 commit
  19. 13 Jun, 2011 1 commit
  20. 24 May, 2011 1 commit
  21. 16 May, 2011 1 commit
  22. 28 Jan, 2011 1 commit
  23. 13 Dec, 2010 1 commit
  24. 04 Dec, 2010 1 commit
  25. 01 Dec, 2010 1 commit
  26. 17 Nov, 2010 1 commit
  27. 16 Nov, 2010 1 commit
  28. 12 Nov, 2010 1 commit
  29. 09 Nov, 2010 1 commit
  30. 23 Oct, 2010 1 commit
  31. 16 Sep, 2010 1 commit
  32. 07 Sep, 2010 1 commit
  33. 25 Aug, 2010 1 commit
  34. 18 Aug, 2010 1 commit
  35. 17 Aug, 2010 2 commits