summaryrefslogtreecommitdiffstats
path: root/Demo/metaclasses/Eiffel.py
blob: 38ee6bc689b39f8564bc7bce8c8ea5c5213a8893 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
"""Support Eiffel-style preconditions and postconditions.

For example,

class C:
    def m1(self, arg):
	require arg > 0
	return whatever
        ensure Result > arg

can be written (clumsily, I agree) as:

class C(Eiffel):
    def m1(self, arg):
	return whatever
    def m1_pre(self, arg):
	assert arg > 0
    def m1_post(self, Result, arg):
	assert Result > arg

Pre- and post-conditions for a method, being implemented as methods
themselves, are inherited independently from the method.  This gives
much of the same effect of Eiffel, where pre- and post-conditions are
inherited when a method is overridden by a derived class.  However,
when a derived class in Python needs to extend a pre- or
post-condition, it must manually merge the base class' pre- or
post-condition with that defined in the derived class', for example:

class D(C):
    def m1(self, arg):
	return whatever**2
    def m1_post(self, Result, arg):
	C.m1_post(self, Result, arg)
	assert Result < 100

This gives derived classes more freedom but also more responsibility
than in Eiffel, where the compiler automatically takes care of this.

In Eiffel, pre-conditions combine using contravariance, meaning a
derived class can only make a pre-condition weaker; in Python, this is
up to the derived class.  For example, a derived class that takes away
the requirement that arg > 0 could write:

    def m1_pre(self, arg):
	pass

but one could equally write a derived class that makes a stronger
requirement:

    def m1_pre(self, arg):
	require arg > 50

It would be easy to modify the classes shown here so that pre- and
post-conditions can be disabled (separately, on a per-class basis).

A different design would have the pre- or post-condition testing
functions return true for success and false for failure.  This would
make it possible to implement automatic combination of inherited
and new pre-/post-conditions.  All this is left as an exercise to the
reader.

"""

from Meta import MetaClass, MetaHelper, MetaMethodWrapper

class EiffelMethodWrapper(MetaMethodWrapper):

    def __init__(self, func, inst):
	MetaMethodWrapper.__init__(self, func, inst)
	# Note that the following causes recursive wrappers around
	# the pre-/post-condition testing methods.  These are harmless
	# but inefficient; to avoid them, the lookup must be done
	# using the class.
	try:
	    self.pre = getattr(inst, self.__name__ + "_pre")
	except AttributeError:
	    self.pre = None
	try:
	    self.post = getattr(inst, self.__name__ + "_post")
	except AttributeError:
	    self.post = None

    def __call__(self, *args, **kw):
	if self.pre:
	    apply(self.pre, args, kw)
	Result = apply(self.func, (self.inst,) + args, kw)
	if self.post:
	    apply(self.post, (Result,) + args, kw)
	return Result
    
class EiffelHelper(MetaHelper):
    __methodwrapper__ = EiffelMethodWrapper

class EiffelMetaClass(MetaClass):
    __helper__ = EiffelHelper

Eiffel = EiffelMetaClass('Eiffel', (), {})


def _test():
    class C(Eiffel):
	def m1(self, arg):
	    return arg+1
	def m1_pre(self, arg):
	    assert arg > 0, "precondition for m1 failed"
	def m1_post(self, Result, arg):
	    assert Result > arg
    x = C()
    x.m1(12)
##    x.m1(-1)

if __name__ == '__main__':
    _test()