Closed GoogleCodeExporter closed 8 years ago
Can we please make it @Dynamic & @Mixed and have it available in any Groovy code
Original comment by alex.tka...@gmail.com
on 19 Feb 2011 at 5:52
in the case of gpp, since it's static by default, it make case to have
dynamic/mixed to "escape" the static nature.
since .groovy is dynamic by default, what would be the usage case to use
dynamic/mixed?
Original comment by wmacgy...@gmail.com
on 19 Feb 2011 at 6:20
@Typed class A {
def staticMethod () {}
@Dynamic def dynamicMethod () {}
}
Original comment by alex.tka...@gmail.com
on 19 Feb 2011 at 6:42
Hi Chanwit, did you send this patch by an email separately, by any chance?
If not, could you please send it? It will be good to have shorter annotations
@Dynamic/@Mixed/@Static enabling various compilation modes in Groovy++.
Original comment by roshanda...@gmail.com
on 30 May 2011 at 6:36
I am submitting it.
Two annotations in this patch are made lower cases. (It does not have @static
yet.)
Refactoring their names is trivial, anyway.
Sorry that I didn't have time enough to finish their test cases.
Original comment by chanwit
on 30 May 2011 at 1:20
Attachments:
Original comment by alex.tka...@gmail.com
on 30 May 2011 at 1:25
Thanks for the patch, Chanwit.
I added some tests for covering usage of @Dynamic/@Mixed in both groovy/gpp
files and here is the final commit:
https://github.com/roshandawrani/groovypp/commit/3dd088f08704206433789a778194ebe
4cf6812fa
Original comment by roshanda...@gmail.com
on 2 Jun 2011 at 7:15
I am wondering that for consistency, whether we should also have @Static.
The previous patch is based on having @Typed / @Mixed / @Dynamic.
Original comment by roshanda...@gmail.com
on 2 Jun 2011 at 7:21
IMHO, @Static would be confusing with the semantics of the Java's static. So I
am not sure about having this annotation.
(My usage is with .gpp - not .groovy - and it's statically typed by default.)
Original comment by chanwit
on 2 Jun 2011 at 7:37
Original comment by roshanda...@gmail.com
on 2 Jun 2011 at 1:16
Original issue reported on code.google.com by
chanwit
on 19 Feb 2011 at 12:02