Prev: data plot + gradient + y-intercept
Next: Problem with mex files in Wavelab
From: Walter Roberson on 8 Feb 2010 15:14
Helen wrote:
> Thanks and to be honest I can't answer your question. The array is
> whatever "textread" creates. I can no longer count the number of 2007
> scripts that are now broken. What happened to backward compatibility?
> For 12 years matlab worked easily and flawlessly over a wide range of
> conditions and purposes. Now it seems everything is broken. Wow.

I haven't been able to trace it back any further, but the current behaviour of
textread() of producing a cell array of strings when the format element is
"%s", existed at least as early as Release 13 Service Pack 2 (6.5.2)
http://www.mathworks.com/access/helpdesk_r13/help/techdoc/ref/textread.html

textread() is not one of the functions listed as having changed between 6.1
and 6.5
http://www.mathworks.com/access/helpdesk_r13/help/base/relnotes/matlab/matlab1312.html

Release 6.1 was released in mid December 2001, more than 8 years ago, and 5
years before you started writing those 2007 scripts.


Possibly you have been accustomed to using the '%c' format element instead of
the '%s' format element.
From: Helen on 8 Feb 2010 21:50
Thanks to Walter and everyone else who has replied. Thanks especially for your patience in the face of my crankiness. I will examine my old textread scripts and see if I can articulate precisely how their behavior appears to have changed. It seems that, yes, nanmean is also historically part of the stats toolbox. Fair enough.

My print command is now working and I appreciate everyone's helpful responses.

Regards,
helen

Walter Roberson <roberson(a)hushmail.com> wrote in message <hkprql$imm$1(a)canopus.cc.umanitoba.ca>...
> Helen wrote:
> > Thanks and to be honest I can't answer your question. The array is
> > whatever "textread" creates. I can no longer count the number of 2007
> > scripts that are now broken. What happened to backward compatibility?
> > For 12 years matlab worked easily and flawlessly over a wide range of
> > conditions and purposes. Now it seems everything is broken. Wow.
>
> I haven't been able to trace it back any further, but the current behaviour of
> textread() of producing a cell array of strings when the format element is
> "%s", existed at least as early as Release 13 Service Pack 2 (6.5.2)
> http://www.mathworks.com/access/helpdesk_r13/help/techdoc/ref/textread.html
>
> textread() is not one of the functions listed as having changed between 6.1
> and 6.5
> http://www.mathworks.com/access/helpdesk_r13/help/base/relnotes/matlab/matlab1312.html
>
> Release 6.1 was released in mid December 2001, more than 8 years ago, and 5
> years before you started writing those 2007 scripts.
>
>
> Possibly you have been accustomed to using the '%c' format element instead of
> the '%s' format element.
From: Pekka Kumpulainen on 9 Feb 2010 03:30
"Helen " <helenfromsun(a)gmail.com> wrote in message <hkqihe$h6a$1(a)fred.mathworks.com>...
> Thanks to Walter and everyone else who has replied. Thanks especially for your patience in the face of my crankiness. I will examine my old textread scripts and see if I can articulate precisely how their behavior appears to have changed. It seems that, yes, nanmean is also historically part of the stats toolbox. Fair enough.
>
> My print command is now working and I appreciate everyone's helpful responses.
>
> Regards,
> helen

Now if you are examining your old scripts you might want to get rid of all textread functions. Documentation of textread has suggested using textscan instead for years now, moving to more serious form of warning in each release.
In 2008b:
Note The textscan function is intended as a replacement for both textread and strread.

And in 2010a prerelease:
Note textread will be removed in a future version. Use textscan instead.
First  |  Prev  | 
Pages: 1 2 3 4
Prev: data plot + gradient + y-intercept
Next: Problem with mex files in Wavelab