[Octave-bug-tracker] [bug #39073] java_get wrong return type

[Philip Nienhuis]

Update of bug #39073 (project octave):

                Category:         Octave Function => Libraries              

    _______________________________________________________

Follow-up Comment #1:

That probably happens because of auto-boxing and -unboxing.

There were a few threads on it in the maintainers list. See e.g., here:
https://mailman.cae.wisc.edu/pipermail/octave-maintainers/2012-December/031440.html
--and especially--
https://mailman.cae.wisc.edu/pipermail/octave-maintainers/2013-January/031844.html

Background:
That it worked in the OF Java package and not in current core dev Octave is
because the boxing/unboxing scheme has been made "Matlab compatible".
Initially I also frowned on this (believe me) but up till now all delicate
Java calls in the io package (of which I'm the maintainer), especially to UNO
(LibreOffice etc), could be gotten to work properly with that new
ML-compatible scheme. In the end, that is :-) - after all 3.7.x is a
development version where things can break any moment.
FYI that you sometimes only get "Java Object> rather than <Java Object: <Java
Class>> doesn't imply 1:1 that Java can't cope with it.

I interpret all of this as "Only if your specific Java method doesn't work
with doubles handed to it from Octave this bug would be valid." 
You mention that you cannot get your Java method to work, so the above seems
valid. Can you invoke the Java method in question with javaMethod? (I wonder
if it would make any difference)

Do you have a simple test case the devs can try (and debug?)
Do you also have access to the Java source code for your methods to see what
class it expects exactly?

(Category set to "Libraries")


    _______________________________________________________

Reply to this item at:

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

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