[Subversion] / PEAK-Rules / Criteria.txt  

Log of /PEAK-Rules/Criteria.txt

Parent Directory

No default branch
Bookmark a link to HEAD: (view) (download)


Revision 2737 - (view) (download) - [select for diffs]
Modified Sat Apr 4 03:15:22 2015 UTC (8 years, 11 months ago) by pje
File length: 39046 byte(s)
Diff to previous 2683
More Python 3 repr fixes

Revision 2683 - (view) (download) - [select for diffs]
Modified Fri Aug 20 13:54:01 2010 UTC (13 years, 7 months ago) by pje
File length: 39084 byte(s)
Diff to previous 2680
Allow nested tuples to mean the "or" of their contents, so that you can 
do things like when(f, (a, (b,c))) instead of having to write a when() 
for (a,b) and a second one for (a,c).

Revision 2680 - (view) (download) - [select for diffs]
Modified Wed Aug 18 05:16:43 2010 UTC (13 years, 7 months ago) by pje
File length: 38178 byte(s)
Diff to previous 2651
Drop superfluous Conjunction subclasses in favor of just using 
Conjunction in the first place.  Classes and NotObjects were a holdover 
from when I thought the right side of a Test would determine what kind 
of operation would be performed and how it would be indexed.

Revision 2651 - (view) (download) - [select for diffs]
Modified Wed Aug 11 00:11:48 2010 UTC (13 years, 7 months ago) by pje
File length: 38307 byte(s)
Diff to previous 2643
Doc tweaks, link fixes

Revision 2643 - (view) (download) - [select for diffs]
Modified Tue Aug 3 01:25:11 2010 UTC (13 years, 7 months ago) by pje
File length: 38016 byte(s)
Diff to previous 2637
Typos.

Revision 2637 - (view) (download) - [select for diffs]
Modified Mon Aug 2 20:17:03 2010 UTC (13 years, 7 months ago) by pje
File length: 38016 byte(s)
Diff to previous 2566
Whack a bunch of spurious doctest failures on different platforms/python versions

Revision 2566 - (view) (download) - [select for diffs]
Modified Tue Jul 15 16:49:02 2008 UTC (15 years, 8 months ago) by pje
File length: 38315 byte(s)
Diff to previous 2553
Refactor condition negation by adding negate() GF, dropping
truth mode from builders, and adding an OrElse sequential-or
operator.  This also changed how Truth tests are coded, to use
Value(True, T/F) objects in place of bools (to get rid of the
ambiguity that previously existed).  Value(x, False) objects
no longer have disjuncts, since that was another ambiguity.
These ambiguities meant that you couldn't cleanly take the
disjuncts() of a Test(), which meant you also couldn't negate
a test safely.  We also no longer force Signature() objects
to expand Test disjunctions, as this isn't necessary for
DNF handling.  (Because we're going to grab the disjuncts()
at rule-add time anyway -- eager expansion was an unnecessary
holdover from the way RuleDispatch did things.)  See also:

 http://www.eby-sarna.com/pipermail/peak/2008-July/003000.html

for more background on the reasoning behind these changes.

Revision 2553 - (view) (download) - [select for diffs]
Modified Tue Jun 17 16:45:50 2008 UTC (15 years, 9 months ago) by pje
File length: 32134 byte(s)
Diff to previous 2548
Tweak a couple of tests for better compatibility across multiple
Python versions (2.3 and 2.4 sometimes print things in a different
order than 2.5 does).

Revision 2548 - (view) (download) - [select for diffs]
Modified Wed Jun 11 17:33:44 2008 UTC (15 years, 9 months ago) by pje
File length: 32120 byte(s)
Diff to previous 2547
Implement remaining intersection rules for istype()+classes

Revision 2547 - (view) (download) - [select for diffs]
Modified Wed Jun 11 16:51:06 2008 UTC (15 years, 9 months ago) by pje
File length: 31453 byte(s)
Diff to previous 2491
Preliminary istype() support for predicate dispatch.
This is just the necessary compiler support for translating expressions
of the form ``type(x) is y`` and ``x in istype(y)``, some support for
istype() implication/intersection with Class criteria, and a bit of 
cleanup/refactoring of the indexing code.

NOT supported: mixing istype() and Classes...  or actually indexing 
istype() criteria.  The entire BitmapIndex system is going to have to be 
refactored in order to fully fix this.  :(  On the bright side, that 
will let me clean up a bunch of other index-related cruft, too.

Revision 2491 - (view) (download) - [select for diffs]
Modified Thu Jan 24 01:27:34 2008 UTC (16 years, 2 months ago) by pje
File length: 28573 byte(s)
Diff to previous 2465
Fix a problem with implication between conjunctions (such
as Signature objects).  This fixes the AmbiguousMethods
problem reported on the PEAK list by Scott Graham.

Revision 2465 - (view) (download) - [select for diffs]
Modified Mon Dec 31 14:58:42 2007 UTC (16 years, 3 months ago) by pje
File length: 28501 byte(s)
Diff to previous 2462
Fix an ambiguity in intersection rules for conjunctions and
disjunctions, and a problem comparing IsObject pointers and
non-integers.  Add an 'engine' argument to tests_for, so that
predicate engines will be able to turn type tuples into
signatures using their argument info.

Revision 2462 - (view) (download) - [select for diffs]
Modified Mon Dec 31 02:03:34 2007 UTC (16 years, 3 months ago) by pje
File length: 28076 byte(s)
Diff to previous 2318
Add shortcut for creating inequalities (Range or Value)

Revision 2318 - (view) (download) - [select for diffs]
Modified Wed Jun 27 14:49:41 2007 UTC (16 years, 9 months ago) by pje
File length: 27773 byte(s)
Diff to previous 2313
Doc cleanups.

Revision 2313 - (view) (download) - [select for diffs]
Added Sun Jun 24 02:05:15 2007 UTC (16 years, 9 months ago) by pje
File length: 27257 byte(s)
PEAK-Rules is now as "smart" as RuleDispatch, in that it now
"knows" as much as RuleDispatch does about logical conditions
regarding Python objects, and how to index them efficiently.
The machinery is also better documented (and probably better
tested) than the equivalent bits of RuleDispatch.

Alas, this does not mean that you can actually use Python
expressions for generic function criteria yet, as the actual
tree builder/interpreter hasn't been written.  So we can
evaluate and index expressions, but not build them from an AST
or build/run a dispatch tree from the indexes.  Still, it's
getting *really* close now!

This form allows you to request diffs between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.

  Diffs between and
  Type of Diff should be a

Sort log by:

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help