1. 04 Feb, 2013 1 commit
  2. 03 Feb, 2013 6 commits
  3. 02 Feb, 2013 1 commit
  4. 01 Feb, 2013 2 commits
  5. 29 Jan, 2013 1 commit
  6. 21 Jan, 2013 1 commit
  7. 18 Jan, 2013 1 commit
  8. 10 Jan, 2013 1 commit
  9. 06 Jan, 2013 2 commits
    • Andrei Paskevich's avatar
      put built-in theories and modules under the library path "why3" · 3df85aba
      Andrei Paskevich authored
      In this way, we can always distinguish them from local theories and
      modules. Both 'use Bool' and 'use why3.Bool' are accepted. No support
      for use/clone of built-in modules is done yet, but so far we don't
      needed (the only built-in module is why3.Prelude which is used by
      default).
      
      As of now, one cannot put a file "why3.why" at the root of loadpath,
      since it will be inaccessible. Paths like why3/toto.why are still
      admitted, but we will probably ban them too and reserve the whole
      "why3.xxx.yyy" hierarchy for the built-in theories and modules.
      3df85aba
    • Andrei Paskevich's avatar
      minor · c3357f54
      Andrei Paskevich authored
      c3357f54
  10. 05 Jan, 2013 5 commits
  11. 03 Jan, 2013 1 commit
  12. 24 Dec, 2012 1 commit
  13. 19 Dec, 2012 3 commits
  14. 13 Nov, 2012 3 commits
  15. 12 Nov, 2012 1 commit
  16. 10 Nov, 2012 1 commit
  17. 09 Nov, 2012 1 commit
    • Andrei Paskevich's avatar
      remove program pattern constructors · 29e1d937
      Andrei Paskevich authored
      it is safer to construct the whole pattern from an untyped skeleton
      in a top-down way, than to check the ghostness/mutability on each
      constructor application.
      29e1d937
  18. 08 Nov, 2012 1 commit
  19. 06 Nov, 2012 3 commits
  20. 05 Nov, 2012 1 commit
  21. 04 Nov, 2012 2 commits
  22. 31 Oct, 2012 1 commit