close Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Changes between Version 3 and Version 4 of ContextPy


Ignore:
Timestamp:
01/10/2011 04:33:54 PM (9 years ago)
Author:
malte.appeltauer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ContextPy

    v3 v4  
    11= ContextPy =
    22
     3== Overview ==
    34ContextPy, our context-oriented extension to the [http://www.python.org/ Python] language, provides a COP-based approach to ''design by contract'' (DBC).
    45DBC is a programming technique to separate contract enforcement from application code. DBC provides information about the applicability of methods and helps  to  narrow  down  the  search  space  in  case  of  a  software failure.   However,  most DBC implementations suffer from inflexibility:  Contract enforcement can only be activated or deactivated at compile-time or start-up, contracts are checked globally and cannot be restricted in their scope such as to the current thread of execution,  and contracts
     
    1314ContextPy  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.
    1415
    15 '''Layers'''[[BR]]
    16    In ContextPy layers are represented by regular objects  that  provide  the  identities  layers  need  to  exhibit  at
     16'''Layers'''[[BR]] In ContextPy layers are represented by regular objects  that  provide  the  identities  layers  need  to  exhibit  at
    1717run-time.  Layer access has to be managed by the developers.
    1818