Hey gang...
I've decided to use abc to collect dynamic program behaviour information
(such as points-to sets). One of the things that I will need in all
of my aspects will be a way to get the bytecode offset (and bytecode
location in general) for each single-statement join point.
Should I make this an abc extension, or is it generally useful enough
that we should provide it natively in abc? In the former case, should it
be part of the eaj extension, or a separate extension? Have we decided
how we will handle extension composition? For either case, does anyone
have opinions on where the bytecode information should go? I could
either add it to SourceLocation, or make a new BytecodeLocation and
getter method in JoinPoint and JoinPoint.StaticPart.
On a related note, I was looking at eaj a little bit. In EajFactory,
there are several methods of the form:
foo(parameters) {
super.foo(parameters);
}
Why are they necessary? Shouldn't method dispatch just find them in the
superclass?
Ondrej
Received on Sat Sep 11 23:55:12 2004
This archive was generated by hypermail 2.1.8 : Mon Sep 13 2004 - 02:30:02 BST