[Octave-bug-tracker] [bug #59277] xls2oct and/or openxls behave unexpected

[Dennis]

Follow-up Comment #8, bug #59277 (project octave):

You are right, there is some thread drift. My apologies for that. Do note that
my initial motivation to dig into this was slow behavior. This was due to both
reasons that you summarize.

Having said that, it is good to here that you have a fix for the first issue
(using UNO interface when OCT is specified). I can't use the COM interface,
because the code must run on a Unix system as well.

With regard to issue 2, I understand that proper diligence is required. Can we
make it explicit what that means? What should be tested in order to be sure
that the new code works properly in all cases? 

In addition, I am certainly willing to check the cell2mat("<function name>",
<cell array>, ...) option, but I need some directions. In your code cell2mat
is used for a simple cell array, and no function name is entered. So how does
this apply to this specific usage?

    _______________________________________________________

Reply to this item at:

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

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