Interesting that you called it proxy. We have a similar plan for lombok (used to be at the top of the list, but interesting co- operation with Michael Ernst and the Checker Framework, as well as the closures announcement, has pretty much made the lombok agenda null and void. We're still sorting through things).
We were planning on calling it @Delegate though, and not @Proxy. We chose @Delegate mostly because the term fits (all methods of the type of the @proxy/@Delegate object are copied over, and the implementations are _delegated_ to the object marked @Delegate), there's some precedence (C# uses this term as well), and proxy has other connotations in java (mostly involving dynamically creating an implementation of an interface, with all methods pointing to something akin to a method_missing kind of thing). Intrigued as to why you went with @proxy. Is that a more common term in the functional programming world, or something specific to scala? --Reinier Zwitserloot On Nov 23, 11:39 am, Kevin Wright <[email protected]> wrote: > The autoproxy compiler-plugin for scala is now available to view on > github:http://wiki.github.com/scala-incubator/autoproxy-plugin > > My goal is to take some of the boilerplate pain out of object > delegation, using a code-generation approach similar to project lombok > on Java. > > It's still a bit prototypey at the moment, and is currently based on > the SVN trunk of Scala. > To help with this, an ant script is available to build the plugin. > > My aim is to track Scala release candidates and have the plugin > "officially" released at the same time as Scala 2.8 -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=.
