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

[Philip Nienhuis]

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

Dennis,

Yeah your initial bug report comprised a few issues, no worries, that often
happens. I started to cherry pick the easiest one, interface issues, which as
you described *also* gave rise to slow behavior and was reported elsewhere as
well.
IMO proper functionality is always priority #1, speed comes later.

Then, in my comment #7:
"cell2mat (...)" 
should read
"cellfun (...)"
(I shouldn't keep going on and on after midnight :-( )

"Diligence" - there's a reason that the current sharedStrings access code is
what it is; and I must have various test spreadsheets lying around somewhere
to check with. But again, presently I lack time to sort this all out, even to
make it explicit, I simply have other priorities.
Later on I'm quite prepared (and curious) to pick it up.

As to speed / COM / databases / etc.:
In your workflow, can you write spreadsheet contents to .csv files before
processing?
In the io package there's also csv2cell() that can read mixed .csv files
(numeric and text) and does so blazingly fast. In fact it is what I use at
work to read & process e.g., database exports of millions of lines (far beyond
the limits of even .xlsx files). Once in a cell array data processing is
usually very fast and can even be done in parallel using e.g., parcellfun.


    _______________________________________________________

Reply to this item at:

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

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