[abc-dev] Why are ITD methods woven as they are

From: Wouter De Borger <w.deborger_at_gmail.com>
Date: Wed, 7 May 2008 11:24:15 +0200


I'm trying to figure out why ITD Methods's are woven as they are.

My primary sources of information are decompiled code, ABC source code
 and technical
report No. abc-2004-4
The report says (5.3)

Our implementation strategy leaves the code for intertype methods as static
> methods in the originating aspects. This avoids the use of accessor methods
> for accessing members of the aspect scope (and that is the vantage point for
> visibility tests). Also, the method is then considered as part of the aspect
> for name matching, which is the desired behaviour.

I don't understand the second argument. Can anyone explain this?

BTW: This choice als leads to bug
static methods

Received on Wed May 07 2008 - 10:24:22 BST

This archive was generated by hypermail 2.2.0 : Wed May 07 2008 - 11:10:10 BST