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

[Philip Nienhuis]

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

OK I yield....
But then something must be done about the 2nd FAIL, either the test or the
code. Your pick?

Maybe it is time (for me) to run all the textscan/strread tests through Matlab
again. After all, only now that the limitations of the m-code have vanished we
can strive for max compatibility. I'm not pessimistic BTW, I think at most
we'll only catch rare corner cases like bug #44750.
Trying the example there in Matlab r2016a learns that w/o
multipledelimsasone=1 we get {'', 'home','foo'} and with it we get {'home
'foo'}. Intriguing but I suppose your reasoning is better than mine. Your
observation that no design choice can be 100 % consistent is absolutely
right.

Looking back I've learned a lot about Octave's m-code figuring out how to
reliably parse complicated repeated text patterns. But m-code was never the
best means for what textscan is to get together. I'm happy with leaving the
role of strread/textread/textscan custodian behind me :-)


    _______________________________________________________

Reply to this item at:

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

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