Changes between Version 2 and Version 3 of ContextPy

Timestamp:

01/10/2011 04:33:36 PM (9 years ago)

Author:

malte.appeltauer

Comment:

--

ContextPy

@@ -13 +13 @@
 ContextPy  supports the layer-in-class approach and with that allows developers to define their partial methods within the scope of the actual classes these methods are contributing to. Similar to all other COP extensions so far, ContextPy provides both layers, partial methods, and dynamic scoping. 
 
-'''Layers'''
-In ContextPy layers are represented by regular objects  that  provide  the  identities  layers  need  to  exhibit  at
+'''Layers'''[[BR]]
+   In ContextPy layers are represented by regular objects  that  provide  the  identities  layers  need  to  exhibit  at
 run-time.  Layer access has to be managed by the developers.
 
-=== Layer Composition === 
+'''Layer Composition'''
 The representation of activated and deactivated layers is handled by two stacks—one for thread-
 specific and one for globally activated layers. Layers can be(de-)activated using Python’s with statement or by library
 methods for stack operations.
 
-=== Partial Methods === 
+'''Partial Methods''' 
 In Python, each class has its own dictionary that maps identifiers (keys) to objects (values). For instance, a method is stored with its name as key and the method object as value. We introduce a layered method descriptor that consists of all (partial) methods and a cache