1. 20 Dec, 2011 1 commit
    • Guillaume Melquiond's avatar
      Move Coq realizations from a .ml file to a driver file. · cc79baa8
      Guillaume Melquiond authored
      Note that the file is still generated at compilation time.
      
      The "realized" meta takes two arguments. The first one is the path+name of
      the theory, the second one is the translation of it for the target prover.
      The meta is supposed to be put into a printer file, so there is no
      ambiguity on the target. The second argument can be left empty if it can be
      inferred from the first one.
      
      Note that the first argument is not really satisfactory, since it is
      redundant with the theory part of the driver. Moreover, its handling is a
      bit crude: it does not take into account rich qualifiers and it does not
      generate proper error messages if it does not match the theory.
      cc79baa8
  2. 15 Dec, 2011 3 commits
  3. 14 Dec, 2011 1 commit
  4. 13 Dec, 2011 1 commit
  5. 08 Dec, 2011 2 commits
  6. 06 Dec, 2011 3 commits
  7. 01 Dec, 2011 5 commits
  8. 30 Nov, 2011 10 commits
  9. 29 Nov, 2011 2 commits
  10. 28 Nov, 2011 1 commit
  11. 27 Nov, 2011 2 commits
  12. 26 Nov, 2011 1 commit
  13. 24 Nov, 2011 2 commits
  14. 23 Nov, 2011 3 commits
  15. 20 Nov, 2011 3 commits
    • Guillaume Melquiond's avatar
      Regenerate Coq proofs broken by the support for realizations. · c817c1ca
      Guillaume Melquiond authored
      Note that this is just a consequence of symbols not being imported from
      realizations. If Coq files were generated with "Require Import" directives
      rather than just "Require", the change would have been completely
      transparent. This is not reason enough to switch to "Require Import" but
      it should be kept in mind.
      c817c1ca
    • Guillaume Melquiond's avatar
      Point Coq to Why3 realizations by adding a -R option inside its prover commands. · 32881636
      Guillaume Melquiond authored
      My first idea was to use "-R @libdir@/coq", or some other variable I would
      have defined in configure.in, but it didn't work at all. Indeed, such path
      variables depend on cascaded substitution, which work fine inside
      make files and shell scripts, but not at all inside Why3 config files.
      Note that this is a documented feature of Autoconf so I doubt there is any
      way to circumvent it.
      
      So I ended up adding a new format specifier inside call_provers: %l is
      substituted by Config.libdir.
      32881636
    • Guillaume Melquiond's avatar
      Switch to an always-on realization mode for Coq. · f796cd6d
      Guillaume Melquiond authored
      There are hardly any change to the code. It now just looks whether
      dependencies are marked as realized. The old no-realization mode is
      equivalent to marking no theory as realized, while the old realization
      mode amounts to marking all of the theories as realized. Now, the finer
      granularity make any intermediate state reachable. This is just a proof
      of concept, so the actual set of realized theories is hard-coded.
      f796cd6d