Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Who's developing AspectJ? WAS: [aspectj-dev] Status of IDE integration support in compiler

Hello all,

I subscribe to this list in part because I'm intensely interested in the
details of AspectJ. However, I'm not an AspectJ developer. (In part this is
because I don't have the requisite expertise to work on something like the
compiler). The comment at the end of Jim's email:

> Someone needs to figure out what the correct behavior should be in a
> tricky case like this and implement it.

got me thinking. Who is currently developing on AspectJ? I'm guessing that
Jim and Erik's days of high contribution will likely end with the release
of 1.1. Is there a list of committers? Is anyone other than the original
PARC team regularly contributing source? How is the project governed? (Is
there an Eclipse management style that it subscribes to?) It may be too
early to ask these questions. I'm just rather curious.

Cheers,
nick
--- Jim.Hugunin@xxxxxxxx wrote:
> For the beta4 release, I fixed most of the bugs in the code to build the
> structure models that are used by the different IDE integrations to show
> the crosscutting structure of programs -- so you shouldn't see the
> arbitrary crashes reported in 1.1beta2.
> 
> Part of the fix that I'm dubious about is that some join point shadows
> silently don't appear in the model at all.  I added an Xlint warning
> (shadowNotInStructure) so that users can be informed when this happens. 
> By default it's set to ignore.
> 
> Here's an example of a join point shadow that won't appear in the
> structure:
> 
> class Foo implements Runnable {
>     Foo() { }
> }
> 
> 
> aspect A {
>     before(): initialization(Runnable) { ... }
> }
> 
> The advice in A will run whenever a Foo is constructed because part of
> initializing a class is initializing all of its super classes and
> interfaces.  However, the shadow appears to be in the code for Runnable
> which the compiler doesn't have access to.
> 
> Someone needs to figure out what the correct behavior should be in a
> tricky case like this and implement it.
> 
> -Jim
> _______________________________________________
> aspectj-dev mailing list
> aspectj-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/aspectj-dev


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


Back to the top