Prev: vectorized way to repeat+concatenate data?
Next: Two slices (or imagesc?) without having volume data
From: Oleg Komarov on 2 Jul 2010 12:49
"Jan Simon" <matlab.THIS_YEAR(a)nMINUSsimon.de> wrote in message <i0l2r8$62q$1(a)fred.mathworks.com>...
> Yep, I got it after more and more hysterical clicking in the docs:
> http://www.mathworks.com/access/helpdesk/help/techdoc/rn/rn_intro.html
> I really expect a link on the main support page.
>
> Jan
I knew about that page which goes as far as version 7.
Anyway I'll send TMW the email.

Oleg
From: Matt Fig on 2 Jul 2010 13:22
I have requested this feature and encouraged others to do so for a few years now.

It sure would be nice to have a function history section, either in the help or in the doc for ML functions.
From: Steven Lord on 2 Jul 2010 13:22

"Jan Simon" <matlab.THIS_YEAR(a)nMINUSsimon.de> wrote in message
news:i0l2r8$62q$1(a)fred.mathworks.com...
> Yep, I got it after more and more hysterical clicking in the docs:
> http://www.mathworks.com/access/helpdesk/help/techdoc/rn/rn_intro.html
> I really expect a link on the main support page.

There's no link to the Release Notes directly because they're part of the
documentation. The main documentation is accessible from the main support
page; it's the first one in the Documentation section of the "Browse by
Resource" box in the lower third of the page.

The link to the current release's Release Notes is immediately below the
alphabetical list of all products dropdown on the main documentation page.
To access product-specific release notes (if the product has any for the
current release) click on a product's name in the list on the main
documentation page -- if it has Release Notes they will be linked under
What's New on the product's page.

Since I see later in the thread that someone is interested in Release Notes
back farther than release R14 (which is the earliest you can access directly
from the current documentation), if you scroll down to the bottom of the
main documentation page, you can read the documentation for release R13SP2,
and at least some of the products' Release Notes (definitely MATLAB and
Simulink, I checked) in that documentation include information going back to
release R12 (which is close to ten years old.)

--
Steve Lord
slord(a)mathworks.com
comp.soft-sys.matlab (CSSM) FAQ: http://matlabwiki.mathworks.com/MATLAB_FAQ
To contact Technical Support use the Contact Us link on
http://www.mathworks.com


From: Kelly Kearney on 2 Jul 2010 14:54
"Matt Fig" <spamanon(a)yahoo.com> wrote in message <i0l77s$n0e$1(a)fred.mathworks.com>...
> I have requested this feature and encouraged others to do so for a few years now.
>
> It sure would be nice to have a function history section, either in the help or in the doc for ML functions.

I've also requested this feature. My request arose out of a help request I sent trying to determine if any changes had been made to a particular function in recent releases. There had indeed been minor changes that had never been included in the release notes (only a major changes are documented there), and that did affect my code running on an older version.

The service representative rather unhelpfully told me that it was not their policy to document anything other than major changes and bug fixes, and I could find history information by comparing the revision number and date of the m-files in my older version with the newest releases. However, this is obviously impossible to do if you do not own every release of Matlab. Seeing that the Mathworks *does* have a copy of every release (or at least, I assume they do), I would think it would be a pretty straightforward task to parse the revision number out of each function for each release. That way, we could have a documented list of when a function was changed. Just the bare list of version numbers would let users see when a particular function was introduced/removed, and whether small or larger changes were made to the function between releases.

Details of what changed would be a nice bonus, but obviously this would require significantly more work, so I won't be greedy.

-Kelly
From: Jan Simon on 2 Jul 2010 16:00
Dear Kelly,

> The service representative rather unhelpfully told me that it was not their policy to document anything other than major changes and bug fixes, and I could find history information by comparing the revision number and date of the m-files in my older version with the newest releases.

I'm sure, that the service representative was correct: it was not their policy.
Without doubt Matlab has left the status of software for dedicated students. For a tool, which is applied in a broad field of scientific work, it is very important to document changes as exact as possible to support the reproducibility of results.
Therefore it is time, although it is late, to change the policy and include exhaustive documentation of *all* changes, even if they seem minor.

> Details of what changed would be a nice bonus, but obviously this would require significantly more work, so I won't be greedy.

Matlab is fortuantely used in many labs. If a scientist want to share, sell, develop code with others, it is necessary to have the ability to control differences between Matlab releases. Scientific working is based on reproducibility, therefore a detailed list of changes is not just a nice bonus, but basic.

BTW, when did FIND start to understand the 'first' flag?

Jan
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: vectorized way to repeat+concatenate data?
Next: Two slices (or imagesc?) without having volume data