Hi Daniel, I think the majority of Groovy users have in their mind that Groovy is just like Java, only better. :-) So, initially we should aim to be the same as Java.
Depending on what we discover during experimenting/implementation, we might alter that plan. We might stop short if there are things we think are extremely unlikely to be used in Groovy or particularly hard to do. We might also go further if we find an interesting extension but it would have to make sense for Groovy and not cause potential incompatibilities with Java. Any changes from Java would always be mailing list discussion material anyway. Cheers, Paul. On Tue, Jun 13, 2017 at 11:28 PM, Daniel Sun <[email protected]> wrote: > Hi Paul, > > I'm reading an article on JSR308, which is really useful. > http://www.oracle.com/technetwork/articles/java/ > ma14-architect-annotations-2177655.html > > In addition, I've already created a branch > jsr308(https://github.com/danielsun1106/groovy-parser/tree/jsr308) to > experiment the grammar. Before working on it, I want to confirm whether > Groovy will support JSR308 fully. > > P.S. The following code is quite strange for me ;-) > Forecast @Readonly [] fiveDay = new Forecast @Readonly [5]; > > Cheers, > Daniel.Sun > > > > -- > View this message in context: http://groovy.329449.n5. > nabble.com/JSR-308-support-for-Groovy-tp5741586p5741627.html > Sent from the Groovy Users mailing list archive at Nabble.com. >
