[Octave-bug-tracker] [bug #47480] [octave forge] (io) relies on deprecated octave_config_info

[Philip Nienhuis]

Follow-up Comment #11, bug #47480 (project octave):

Mike,

Reminiscences are slowly coming back, sorry for that. It's code I wrote years
ago, that has always worked; originally it was even in PKG_ADD.

_usejava_ 
That's a good alternative, thanks. IIRC I wrote (large parts of) usejava.m.
usejava('jvm') checks if Java works at all in Octave, rather than just if Java
support was built-in. The former is what is needed.
I know of other places in the io package code where this would be a better
solution.

_libdir_
Ah, now I understand what you meant with "...jar files will be dropped into
the Octave library directory on Windows" (comment #7). At the time from before
mxe-octave, file hierarchy in mingw was less rigid, having Java .jars live in
/lib was not so strange and even convenient.
Maybe it's still be a good place, so is there an alternative for
octave_config_info("libdir")? It doesn't hurt to search there for .jars

_ENABLE_64_
uname().machine would do as well.
Fortran indexing bit width doesn't matter here, it's just that the bit widths
(arch) of Octave, Java and LibreOffice should all match.

Thanks for the suggestions. 
I suppose the code needs to be amended or octave-6.+? I expect current
io-2.4.12 to be still working with upcoming Octave-5.1.0.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?47480>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/