Re: Textscan Stops for Missing Data

[PhilipNienhuis]

Ozzy:


Ozzy Lash wrote
> Have you tried setting the "WhiteSpace" option so that it doesn't include
> \t?  I see different behavior with that.  The only problem is, your file
> has a few lines that start with a tab, and that trows the processing off.
> If I get rid of those tabs, it reads 110 entries.
> 
> The argument I used was "WhiteSpace", " \b\n\r"
> 
> Reading the documentation is strread for I see the default is " \b\n\r\t"
> ,
> Reading that documentation, it does say:
> 
>           Whitespace is
>           always added to the set of delimiter characters unless at
>           least one "%s" format conversion specifier is supplied; in
>           that case only whitespace explicitly specified in "delimiter"
>           is retained as delimiter and removed from the set of
>           whitespace characters.  If whitespace characters are to be
>           kept as-is (in e.g., strings), specify an empty value (i.e.,
>           "") for "whitespace"; obviously, whitespace cannot be a
>           delimiter then.
> 
> Which is a bit confusing to me, but it sounds like, if there were a %s
> conversion, the \t might get deleted from the whitespace values.  It seems
> like it might make sense to always do that.

Sorry but it looks like you're a bit confused?
strread.m isn't the engine behind textscan anymore.
Nowadays textscan is a separate, binary function and as such much faster
than the combo textscan.m+strread.m used to be.

Philip



--
View this message in context: 
http://octave.1599824.n4.nabble.com/Textscan-Stops-for-Missing-Data-tp4684655p4684680.html
Sent from the Octave - General mailing list archive at Nabble.com.