> Of course, the much cooler tool that's part of that concept is the > reverse: It'll take standard run-of-the-mill java code and offers to > replace all that boilerplate with nice, concise lombok annotations.
That's the idea you presented for us originally I seem to remember, but where I personally wonder whether you'll be able to capture enough (and the right) intent. Where I think this gets really interesting is how it potentially can be used as a migration mechanism, sparking some innovation and life into Java again. For instance, have it perform transformations on usages of deprecated API's (lombok @Transformation annotation to supplement @deprecated?). It would then be ok to truly deprecate (remove) stuff, as long as you have transformation rules in place. Old source could then still compile against most recent API and language. /Casper --~--~---------~--~----~------------~-------~--~----~ 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=en -~----------~----~----~----~------~----~------~--~---
