1. 01 Nov, 2013 3 commits
  2. 28 Oct, 2013 1 commit
  3. 27 Aug, 2013 4 commits
  4. 26 Aug, 2013 1 commit
  5. 25 Aug, 2013 1 commit
  6. 17 Jul, 2013 1 commit
  7. 13 May, 2013 2 commits
  8. 25 Mar, 2013 1 commit
  9. 21 Mar, 2013 1 commit
  10. 16 Mar, 2013 1 commit
  11. 14 Mar, 2013 1 commit
  12. 08 Mar, 2013 2 commits
  13. 07 Mar, 2013 6 commits
  14. 06 Mar, 2013 1 commit
  15. 22 Feb, 2013 1 commit
  16. 01 Feb, 2013 1 commit
  17. 21 Jan, 2013 1 commit
  18. 06 Jan, 2013 1 commit
    • 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
  19. 07 Dec, 2012 1 commit
  20. 28 Nov, 2012 2 commits
  21. 09 Nov, 2012 1 commit
  22. 31 Oct, 2012 2 commits
  23. 30 Oct, 2012 3 commits
  24. 29 Oct, 2012 1 commit