Loom Alpha 3 Posted

[maxim.porges]

Hey guys,

I got some of the issues with yesterday's release fixed tonight, and
replaced the sample app with the latest build.

ITEMS FIXED
- Methods accepting ...rest arguments are now fully advisable.
The ...rest argument is passed in the MethodInvocation arguments in
the appropriate position, and is an array just like if you were
dealing with ...rest directly.
- Methods accepting optional arguments are now advisable. You will
always get all the parameters regardless of how the method is called,
i.e. you'll get the default values for optional parameters if no
explicit values are passed for those optional parameters. This is
different from how the "arguments" object is usually passed on a
method with optional arguments, but seemed more useful since you can
get the default values as if you were operating within the original
method invocation.

ONGOING KNOWN ISSUES/LIMITATIONS (ordered by priority)
- Setters/Getters fail when called
- Methods with custom namespace declarations fail when called
- Static class methods defer to the superclass implementation and
are not proxied

I have some ideas for the getter/setter issue, but I'm still
experimenting for the best fit. If I had a few extra hours tonight I
would get this finished too, but it looks like this will have to wait
until the weekend.

I wanted to ask: for the static class method advice, there would have
to be a static handler method since all the handler code today is
instance-based, which I did on purpose as a feature so that you could
advise individual instances differently if you wanted to (unlike
AspectJ where the advice is always statically woven). What do you guys
think about a Loom-namespaced static method called setStaticHandler()
for this use case? Any other ideas?

Thanks,

- max