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

[Philip Nienhuis]

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

A while ago (1,5 year ago?) there was a discussion on this as java_get and
java_set were deleted as those functions weren't Matlab compatible. In bug
#41239 it was decided to reinstate them.

IIRC the core devs rather wanted OO-like syntax. But currently Octave does not
support that for static Java stuff, so in the end __java_get__ and
__java_set__ were reprieved for 4.2 or until a better Matlab-compatible
solution was in place.
Hopefully __java_get__ and __java_set__ will survive 4.2 and maybe even 4.4
:-)

Ernst, I'm in favor of your solution, but it is and remains a temporary fix.

One more thing:
Maybe it is even better to keep __java_set__ / __java_get__ but provide other
binary DEFUNs that just call them; much like javaMethod for a while was
calling java_invoke() until the latter was finally deprecated (it is still in
4.0.x).
The reason for this suggestion is that there can be quite a bit of code around
(not only the io package) that changed to __java_get__ when java_get got
deprecated and deleted. Completely removing it would leave that code in the
rain. 



    _______________________________________________________

Reply to this item at:

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

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