I think this is a really good idea.

Can you look at turning some of the example uses that you have posted here into a new test suite entry, say test/java.tst?

Tests might look like

%!testif HAVE_JAVA; usejava ("jvm")
%! assert (jobj.getStringAsString (), "Hello, world!")
%!testif HAVE_JAVA; usejava ("jvm")
%! assert (jobj.getInt (), int32 (42))
...

There are a few outstanding bugs related to Octave/Java value boxing behavior.

• https://savannah.gnu.org/bugs/index.php?54170
• https://savannah.gnu.org/bugs/index.php?53524
• https://savannah.gnu.org/bugs/index.php?51822
• https://savannah.gnu.org/bugs/index.php?51804
• https://savannah.gnu.org/bugs/index.php?48820
• https://savannah.gnu.org/bugs/index.php?48817
• https://savannah.gnu.org/bugs/index.php?42701
• and so on

Many of these are having to provide their own example Java code, which you need to download and compile if you want to reproduce their use case.

It might be useful to have a canonical Java value-boxing test that provides a bunch of example method signatures to run tests against, so you can have a shared agreed-upon test context, and not have to bother compiling custom Java code to reproduce test cases.

I've attached a changeset which defines a new org.octave.BoxingTester class that provides several permutations of Java method signatures that you can use to exercise the Octave/Java value boxing behavior.

Example:

octave:1> tst = javaObject ("org.octave.BoxingTester")
tst =

<Java object: org.octave.BoxingTester>

octave:2> tst.foo(42)
foo(double): (42.0)
ans = [](0x0)
octave:3> tst.foo ([42, 43])
foo(double[]): ([D@27f674d)
ans = [](0x0)
octave:4> tst.foo("Hello, world!")
foo(String): (Hello, world!)
ans = [](0x0)
octave:5> tst.getStringAsString
ans = Hello, world!
octave:6> class(ans)
ans = char
octave:7> tst.getStringAsObject
ans = Hello, world!
octave:8> class(ans)
ans = char