I did not have this portability problem in mind. But it seems that "annotations" in pre java 1.5 (1.3/1.4) are possible:
http://backport175.codehaus.org/ http://blogs.codehaus.org/people/avasseur/archives/001121_aspectj_aspect_and_java_13.html 2009/1/26 Oberhuber, Martin <[email protected]> > Interesting. > > I'm all in favor of semantic markup that makes written programs more > expressive, i.e. better convey the programmer's intent. This allows for > better automatic correctness checks, and refactorings. > > I have mentioned a few times already that I'd consider using Generics as > much as possible a big plus. Aspects are similar in some sense. Up to now, > the blocker has always been that there is some interest (not sure if > requirement) to > > 1. Build and run Eclipse out-of-the-box on unmodified stock JVMs, and > 2. Build and run Eclipse (the core pieces) on J2ME micro JVMs (which > are unfortunately on Java1.4 level without Generics). > > For Generics, tools like Retroweaver would allow compiling Java5 Sources > into Java1.4 compatible binaries. And at Eclipse, we are in the fortunate > situation that we "own" a Java compiler (ecj) which - I've been told - even > has the undocumented -jsr14 switch for compiling generics into Java1.4 > binaries. > > In terms of annotations, however, I'm not sure if such "back-compiling" is > possible since the classfile format needs to support the annotations. > > Cheers, > -- > *Martin Oberhuber*, Senior Member of Technical Staff, *Wind River* > Target Management Project Lead, DSDP PMC Member > http://www.eclipse.org/dsdp/tm > > > > ------------------------------ > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Erdal Karaca > *Sent:* Montag, 26. Jänner 2009 09:43 > *To:* E4 Project developer mailing list > *Subject:* Re: [e4-dev] dependency injection through (equinox) aspects? > > > There are other cases where aspects combined with annotations can be used > efficiently: > > E.g., instead of writing > > public void myUICode() { > Display.syncExec( new Runnable() { > public void run() { > ... do something > } > } ); > } > > you would just do... > > @RunInUI( sync = true ) > public void myUICode() { > ... do something > } > > There are many other use cases like this one... > > > > _______________________________________________ > e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/e4-dev > >
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
