1. 21 Jan, 2013 5 commits
  2. 18 Jan, 2013 7 commits
  3. 16 Jan, 2013 2 commits
  4. 15 Jan, 2013 5 commits
  5. 14 Jan, 2013 2 commits
  6. 13 Jan, 2013 2 commits
  7. 11 Jan, 2013 1 commit
  8. 10 Jan, 2013 6 commits
  9. 09 Jan, 2013 3 commits
  10. 08 Jan, 2013 1 commit
  11. 07 Jan, 2013 3 commits
  12. 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
  13. 05 Jan, 2013 1 commit