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