[Octave-bug-tracker] [bug #48866] __java_get/set__

[Ernst Reissner]

Follow-up Comment #4, bug #48866 (project octave):

Hi Philip, 
yes, I was part of that discussion. 
The point was, that there was replacement for member invocatinons of java_get,
but not for static ones. 
This is still the case. 
Thus it is not possible to remove java_get. 

A solution would be, to allow java_get for static invocations only, 
otherwise write obj.fieldName. 

As you point out, there is also javaMethod, 
which is analogous: one may write obj.methodName(...) 
but for static invocations one has to stick to javaMethod. 

Since this is completely analogous, 
let us install an analogous solution: 
Complete builtin, no m-files. 

With constructors, it is similar, 
only that there is static form only. 


All these three cases can be fixed 
as soon as the package.class.method/field/none syntax 
can be parsed as classname, field/methodname. 
I think my fix is on the way to that solution. 

@philip: 
my code does not leave anyone in the rain: 
not java_get was removed but __java_get__ was renamed into java_get and the
m-files for java_get were removed. 


Of course, you are right, this is a temporary fix only. 
On the other hand: what to do 

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48866>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/