Log of /PEAK-Rules/setup.py

Parent Directory

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

Update required versions of BytecodeAssembler and DecoratorTools

Allow registering methods for generic functions that aren't imported yet

Revert licenses to ZPL 2.1; drop 'dev' tags from intermediate releases

Require latest BytecodeAssembler

Use development snapshots so SVN isn't required

Register 0.5a1.dev with the cheeseshop

Predicate dispatching, at last!  We don't compile strings yet,
and range dispatching is worse than half the speed of RuleDispatch
with C speedups.  However, most other types of dispatch should be
a good bit faster, and it should be possible to inline more of the
range lookup.

Thread-safety and re-entrant code generation, such that calling a
function that is being regenerated will execute the previous code
for that function.  Simplified Engine protocols for code generation,
etc.

Switch to using peak.util.extremes

Prepare for switch from Aspects to AddOns

Implement bytecode generation for expressions; this is basically 
equivalent to porting a little more than half of ``dispatch.predicates`` 
from RuleDispatch (specifically, the ``ExprBuilder`` class and related 
node types).

Update for DecoratorTools 1.2

Use struct types for rules and action definitions; correct dependencies 
to BytecodeAssembler 0.1 and DecoratorTools 1.1.

Update PEAK-Rules for latest BytecodeAssembler version.

Code generation support (requires dev trunk of BytecodeAssembler).
This completes the core (multiple dispatch) framework features.  Next 
up: cleanup and doc expansion, before moving on to predicate dispatch
and advanced features.

Zero-functionality setup for PEAK-Rules: mostly design docs in README 
plus an outline of the functionality for the core framework in
framework.txt.