Re:Java 9 with GPU processing, Java 10 will be all-OOP witho...
by eternalban on Friday March 30, 2012 @08:36AM
(#3775632)
No, a class's methods are not instances of java.lang.reflect.Method. The latter is simply a 'reflection', per the package name, of first class JVM construct e.g. a reflection on a method.
[ Parent
| on HN ]
Re:Java 9 with GPU processing, Java 10 will be all-OOP witho...
by riffraff on Friday March 30, 2012 @11:13AM
(#3776305)
would you care to explain why this is not enough? You can pass them around, invoke them, get their properties.
The interface may be bad but I'm not sure what is missing.
Re:Java 9 with GPU processing, Java 10 will be all-OOP witho...
by eternalban on Friday March 30, 2012 @01:35PM
(#3777117)
In the original comment, I was merely addressing the misunderstanding of the GP regarding the reflection packages constructs.
The interface is your basic (irreducible) disconnected/unbound procedure invocation API, with all the positive/warts associated. I agree that in principle, we have enough information in the reflection data structure to allow a (specific) JVM implementation to provide a non-standard 'method object' feature. Consensus, possibly? (Good question, really. C. Nutter is one to hit with that one.)