[Octave-bug-tracker] [bug #49510] after an xlswrite the spreadsheet is corrupted

[Philip Nienhuis]

Update of bug #49510 (project octave):

                  Status:          Ready For Test => Fixed                  
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #31:

I see what you mean.

Some background:
What happen when you call xlsread or friends, is that it in turn calls xlsopen
(which will "open" the spreadsheet file") that in turn calls routines that
find out what "external" spreadsheet I/O interfaces are available; "external"
meaning depending on SW outside Octave.
The order in which interfaces are searched is roughly COM, <Java based
interfaces>. 
If no working external interface is found, Octave falls back to OCT (= native
Octave code).

The error you see means that although only COM was requested, and hitherto the
Java based interfaces themselves are disabled, Octave nevertheless searches
for Java. That shouldn't be needed, admittedly, but normally doesn't harm.
However, apparently your Java setup is unsatisfying so you see errors from
Octave routines (not io package routines) invoked by the io package.

I expect similar errors to happen when you try xmlread.m (also in the io
package).

A workaround will be in a next io release - io-2.4.5 has just been released.
But again, AFAIU the issue lies with your Java setup.

I'll close this bug report.


    _______________________________________________________

Reply to this item at:

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

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