Search All of the Math Forum:
Views expressed in these public forums are not endorsed by
NCTM or The Math Forum.
|
|
dpb
Posts:
9,850
Registered:
6/7/07
|
|
Re: The function textscan
Posted:
Mar 28, 2013 5:53 PM
|
|
On 3/28/2013 10:09 AM, Steven_Lord wrote: > "dpb" <none@non.net> wrote in message news:kit8ad$9f$1@speranza.aioe.org... >> On 3/26/2013 4:56 PM, Steven_Lord wrote: >>> "dpb" <none@non.net> wrote in message >>> news:kisv1h$4t2$1@speranza.aioe.org... >>> >>> *snip* >>> >>>> textread(), while deprecated by TMW and not as fully flexible as >>>> textscan() does have some benefits that aren't available otherwise the >>>> primary of which is that it returns "ordinary" double arrays instead >>>> of cell arrays only a la textscan(). That can often be a nice >>>> advantage. >>> >>> I agree that it can be an advantage. It can also be a complication. ...
As an aside, but not to forget it, one additional complication in textscan() is that it has at least a couple of bugs in parsing formats that exist in neither textread() nor Xscanf() that have been discovered through posters having problems parsing files within the last several months (being relatively new and complicated that's not surprising; it's a compliment to the developers there aren't more blatant ones).
I've submitted a bug report on one and another was observed by another TMW employee (I forget specifically who now, it was a sig I didn't recognize iirc) who saw the thread and I presume that person saw that it was added.
--
|
|
|
|