Tue, 24 Aug 2010 19:19:28 +0200 compute names lazily;
blanchet [Tue, 24 Aug 2010 19:19:28 +0200] rev 38699
compute names lazily; there's no point to compute the names of 10000 facts when only 500 are used
Tue, 24 Aug 2010 18:03:43 +0200 clean handling of whether a fact is chained or not;
blanchet [Tue, 24 Aug 2010 18:03:43 +0200] rev 38698
clean handling of whether a fact is chained or not; more elegant and reliable than encoding it in the name
Tue, 24 Aug 2010 16:43:52 +0200 don't backtick facts that contain schematic variables, since this doesn't work (for some reason)
blanchet [Tue, 24 Aug 2010 16:43:52 +0200] rev 38697
don't backtick facts that contain schematic variables, since this doesn't work (for some reason)
Tue, 24 Aug 2010 16:24:11 +0200 quote facts whose names collide with a keyword or command name (cf. "subclass" in "Jinja/J/TypeSafe.thy")
blanchet [Tue, 24 Aug 2010 16:24:11 +0200] rev 38696
quote facts whose names collide with a keyword or command name (cf. "subclass" in "Jinja/J/TypeSafe.thy")
Tue, 24 Aug 2010 15:29:13 +0200 revert this idea of automatically invoking "metisFT" when "metis" fails;
blanchet [Tue, 24 Aug 2010 15:29:13 +0200] rev 38695
revert this idea of automatically invoking "metisFT" when "metis" fails; there are very few good reasons why "metisFT" should succeed when "metis" fails, and "metisFT" tends to "diverge" more often than "metis -- furthermore the exception handling code wasn't working properly
Tue, 24 Aug 2010 22:38:45 +0800 use matching of types than just equality - this is needed in nominal to cope with type variables
Christian Urban <urbanc@in.tum.de> [Tue, 24 Aug 2010 22:38:45 +0800] rev 38694
use matching of types than just equality - this is needed in nominal to cope with type variables
Tue, 24 Aug 2010 15:08:05 +0200 merge
blanchet [Tue, 24 Aug 2010 15:08:05 +0200] rev 38693
merge
Tue, 24 Aug 2010 15:07:54 +0200 cosmetics
blanchet [Tue, 24 Aug 2010 15:07:54 +0200] rev 38692
cosmetics
Tue, 24 Aug 2010 15:06:47 +0200 use a soft time limit for E
blanchet [Tue, 24 Aug 2010 15:06:47 +0200] rev 38691
use a soft time limit for E with a hard limit, "eproof"/"eproof.pl" doesn't show the proof is there's less than 1 second left, yielding "the ATP output is malformed"
Tue, 24 Aug 2010 14:36:29 +0200 make remote ATP versions more robust, by starting with "preferred" version numbers and falling back on any version
blanchet [Tue, 24 Aug 2010 14:36:29 +0200] rev 38690
make remote ATP versions more robust, by starting with "preferred" version numbers and falling back on any version
(0) -30000 -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 +30000 tip