- 22 Feb, 2016 1 commit
-
-
MARCHE Claude authored
also compatible with Coq 8.4
-
- 05 Feb, 2016 1 commit
-
-
Guillaume Melquiond authored
-
- 11 Dec, 2015 1 commit
-
-
David Hauzar authored
-
- 12 Jun, 2015 2 commits
-
-
David Hauzar authored
-
David Hauzar authored
-
- 23 May, 2015 1 commit
-
-
Andrei Paskevich authored
-
- 23 Mar, 2015 1 commit
-
-
MARCHE Claude authored
+ fixed wrong step limit in one session
-
- 20 Mar, 2015 1 commit
-
-
Andrei Paskevich authored
-
- 19 Mar, 2015 1 commit
-
-
MARCHE Claude authored
-
- 18 Feb, 2015 1 commit
-
-
Guillaume Melquiond authored
-
- 17 Feb, 2015 1 commit
-
-
Guillaume Melquiond authored
This commit also removes the laziness for accessing symbols, since they are already in the scope at the time the plugin is loaded.
-
- 16 Feb, 2015 1 commit
-
-
Guillaume Melquiond authored
-
- 02 Sep, 2014 1 commit
-
-
Andrei Paskevich authored
-
- 14 Mar, 2014 1 commit
-
-
Jean-Christophe Filliâtre authored
-
- 14 Jan, 2014 1 commit
-
-
MARCHE Claude authored
-
- 28 Oct, 2013 1 commit
-
-
MARCHE Claude authored
-
- 22 Oct, 2013 1 commit
-
-
MARCHE Claude authored
-
- 16 Apr, 2013 1 commit
-
-
Andrei Paskevich authored
-
- 09 Apr, 2013 2 commits
-
-
Jean-Christophe Filliâtre authored
-
Jean-Christophe Filliâtre authored
-
- 06 Mar, 2013 1 commit
-
-
Andrei Paskevich authored
-
- 04 Mar, 2013 1 commit
-
-
Andrei Paskevich authored
We store in every lsymbol a new integer field ls_constr, equal to zero if the lsymbol is not a constructor, and equal to the number of constructors of the lsymbol's type otherwise. It is allowed to declare or define an lsymbol with ls_constr > 0 as an ordinary function (otherwise algebraic type elimination wouldn't work - though we might still check this in theories), but it is forbidden to use a wrong ls_constr in algebraic type definitions. The ghostness of a match expression is now determined as follows: If at least one branch expression is ghost, then the match is ghost; else if there is only one branch, then the match is not ghost; else if the matched expression is ghost, then the match is ghost; else if at least one pattern matches a ghost field against a constructor with ls_constr > 1 then the match is ghost; else the match is not ghost. We do just enough to recognize obvious non-ghost cases, and make no attempt to handle redundant matches or to detect exhaustive or-patterns in subpatterns.
-
- 08 Jan, 2013 1 commit
-
-
Jean-Christophe Filliâtre authored
-
- 07 Jan, 2013 1 commit
-
-
Jean-Christophe Filliâtre authored
-
- 21 Nov, 2012 1 commit
-
-
Jean-Christophe Filliâtre authored
-
- 06 Nov, 2012 1 commit
-
-
Andrei Paskevich authored
-
- 05 Nov, 2012 1 commit
-
-
Andrei Paskevich authored
-
- 04 Nov, 2012 1 commit
-
-
MARCHE Claude authored
-
- 30 Oct, 2012 1 commit
-
-
Andrei Paskevich authored
-
- 21 Oct, 2012 2 commits
-
-
Andrei Paskevich authored
Util now is a small module containing misc functions.
-
Andrei Paskevich authored
+ rename Debug.Opt to Debug.Args to avoid conflicts
-
- 20 Oct, 2012 1 commit
-
-
Andrei Paskevich authored
+ create AUTHORS file + fix the linking exception in LICENSE + update the "About" in IDE + remove the trailing whitespace + inflate my scores at Ohloh
-
- 18 Sep, 2012 1 commit
-
-
Guillaume Melquiond authored
The empty string is now a recognized configuration filename. It means that the default configuration with an empty loadpath should be loaded. It also means it will not be saved. This removes the need for a WHY3NOCONFIG environment variable and some tricks based on the WHY3LOADPATH variable. This also removes the need for a /dev/null file.
-
- 11 Sep, 2012 4 commits
-
-
Claude Marche authored
-
MARCHE Claude authored
-
MARCHE Claude authored
-
Claude Marche authored
-
- 30 Aug, 2012 1 commit
-
-
Jean-Christophe Filliâtre authored
-
- 23 Jul, 2012 2 commits
-
-
François Bobot authored
shortcuts are defined in why3.conf. They are automatically generated using two mechanism: - a shortcut section in prover-detection-data.conf creates a shortcut for the first prover that match the regexp - the identifier used as family argument for the prover section in prover-detection-data.conf is used as shortcut for the prover. If different sections use the same argument the first one that match an existing prover is used for the shortcut.
-
François Bobot authored
Remove the id in prover that is used only for command-line, use instead the name,version,alternative of the prover. One can also use regular expression (start with ^). "Alt-Ergo,0.92,with arrays" corresponds only to one prover "Alt-Ergo,^0\.9.*,with arrays" correspond to all the Alt-Ergo prover with arrays which version match "0\.9.*" "Alt-Ergo" is the same thing than "Alt-Ergo,^,^" "Alt-Ergo,0.92," corresponds only to one prover with the alternate fields empty "Alt-Ergo,,with arrays" corresponds to "Alt-Ergo,^,with arrays" since the version is never empty. Provers identification are case sensitive even if it is currently more complicated for the user because case-insensitiveness is not sufficient. Specifiying "alt-ergo" for "Alt-Ergo,^,^" is great, but not if there is more than one match. A more general system of shortcut would be more appropriate.
-