IO package: Difference between revisions

Jump to navigation Jump to search
521 bytes added ,  31 January 2020
m (Fix typo)
Line 99: Line 99:
==== 32 vs. 64-bit issues ====
==== 32 vs. 64-bit issues ====


Generally, if you use a Java-based interface for spreadsheet I/O, it doesn't matter much whether you use Octave 32-bit or Octave 64-bit.
Generally, if you use a Java-based interface for spreadsheet I/O, it doesn't matter much whether you use Octave 32-bit or Octave 64-bit, as long as Octave's bit width matches that of the Java JRE. If you want to use the UNO interface (for LibreOffice & OpenOffice.org), also LibreOffice's bit width needs to match that of Octave and the Java JRE.
However, the UNO interface (for LibreOffice & OpenOffice.org) is more pertinent: 64-bit Octave can only use a 64-bit LibreOffice with UNO, same for 32 bit.
So for spreadsheet I/O with Java-based add-on software like e.g., Apache POI, 64-bit Octave requires a 64-bit Java JRE and -if so desired- a 64-bit LibreOffice. The add-on SW itself (Java .jar files) is bit width agnostic.


On Windows, Octave with a loaded Octave-Forge windows package can invoke MS-Excel for spreadsheet I/O but only 32-bit MS-Office; 64-bit MS-Office does not support ActiveX. In this case it doesn't matter much whether Octave is 32-bit or 64-bit.


==== Java example ====
==== Java example ====
99

edits

Navigation menu