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

[Mike Miller]

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

No rush, I am not waiting for an immediate response, just replying to your
points now as I am still fresh on what I looked at in the io package.

> ('build_features').JAVA - needed to know if Java support was built into
Octave

You can use usejava("jvm") to detect whether Java support was built into
Octave and whether the Java runtime can be loaded at the same time. Does
checking this alone break something on Windows? If so, that can be reported
separately and fixed in Octave. That is the whole point of the usejava
function, so if it doesn't work for your needs, that's a bug.

> libdir - where are libraries situated. Not so much for MingW but also for
some Linux distros; maybe sometime in the future for Octave as well if ever
some spreadsheet I/O would move to core

Setting the value of libdir to octave_config_info("libdir") is only done in a
'if (ispc)' section of code, so this is absolutely Windows specific. So this
is part of the logic I don't understand, is the package intentionally looking
for jar files that the user has copied into Octave's lib directory? Is that
documented somewhere as the recommended way to make Java libraries available
to Octave? If that's not true, then there is no need to search libdir on
Windows.

> ENABLE_64 - ( IIRC) needed to avoid 64-bit Octave find & try to invoke
32-bit LO as that might crash Octave. The other way round was more robust
IIRC. I once had 32-bit and 64-bit Octave and 32-bit and 64-bit LO or OOo
installations on the same box (admittedly a weird but not impossible
scenario), IIRC on Linux and Windows.

As I asked before, do you really need to check ENABLE_64 or can you simply
rely on the processor name returned from 'computer' or 'uname'? It seems to me
that ENABLE_64 is irrelevant, only the computer architecture matters. Or are
you saying that it is possible to have Octave compiled for a 64-bit processor
that can still load 32-bit LibreOffice libraries, but only if it's not using
64-bit indexing? Remember that 64-bit indexing is not the same as 64-bit
instruction set.

    _______________________________________________________

Reply to this item at:

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

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