[Octave-patch-tracker] [patch #8783] C++ implementation of textscan

[Lachlan Andrew]

Follow-up Comment #22, patch #8783 (project octave):

Philip,

Thanks for creating the build.  I decided to figure out how I can build my
own, and that kept me too busy to notice your URL and tips re mkoctfile.  Your
additions to the wiki on mxe-octave are really clear.  However, there still
seems to be some black magic involved, but it eventually built.  (If I get
around to it, I'll update the wiki with a "what to do if things go wrong"
section...)

Here is a new patch, that should pass all of the tests under Windows.  The
problem was a bad "if" condition that caused a reference to an uninitialized
look-up table for delimiters.  I have no idea why it worked on Linux. 
Fortunately, it didn't need multiple cross-compiles.

The code I actually tested was my main code in which the function is called
"textscan".  I did a global search-and-replace to xtextscan after taking the
diff, so let me know if it doesn't apply cleanly.

I don't have access to MacOS to test it.  Sourceforge used to have a shared
build farm, but I take it that Savannah doesn't.  If you can test it, please
let me know how it goes.

After that, I suppose the next step is supporting textread etc.  Should we do
them in C++ too, or just as scripts?  I think they have some conversion
specifiers that textscan doesn't.  I'm inclined to make textscan accept more
inputs than Matlab's so that all other functions are simple special cases of
it.  Let me know what you think.

Have fun in the "sprint" if you take part.  I'm in Australia and so will be
asleep when most of you are busy.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?8783>

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