Store 
| Products & Services | Solutions | Academia | Support | User Community | Company |
 |
Download Product Updates | | |  |
Get Pricing | | | |
Trial Software |
| Documentation → MATLAB |
| Products & Services | Solutions | Academia | Support | User Community | Company |
|
Download Product Updates | | | |
Get Pricing | | | |
Trial Software |
| Documentation → MATLAB |
| Contents | Index |
| Learn more about MATLAB |
New features and changes introduced in this version are organized by these topics:
New features and changes introduced in Version 7.3 (R2006b) are described here.
You can run a utility from the Help browser to associate .m, .mat, .fig, .p, and .mdl files with the MATLAB program in the Microsoft Windows operating system. After running the utility, you will be able to start MATLAB by double-clicking any of those file types in Windows Explorer. You can still use Windows Explorer Folder Options to perform these file associations, but the utility makes the task more convenient. For details, see Starting the MATLAB Program using File Associations on Windows Platforms.
When you start MATLAB on platforms running The Open Group UNIX operating system using the -nodesktop startup option, and you redirect output, for example to a file, MATLAB now sends any errors to the shell, while normal output goes to the redirect target. This change was made so that redirection withMATLAB follows standard behavior for the UNIX operating system.
For example:
matlab -nodesktop -"r magic(3), magi(5)" > test.txt
starts MATLAB in nodesktop mode, runs the statement magic(3) and writes the output to test.txt. When MATLAB runs magi(5), execution fails and MATLAB displays the error message in the shell.
Compatibility Considerations. In previous versions, MATLAB redirected both output and error messages, so in the above example, MATLAB wrote the output of magic(3) as well as the error message from magi(5) to test.txt.
If you have shell scripts that use > to redirect output, and you rely on errors appearing in the output target, you need to modify the matlab startup statements in those scripts.
To achieve the former behavior, that is, to redirect both output and errors to the specified target, use that specific redirect syntax for your shell. For example, in tcsh, use >&, as in
matlab -nodesktop -"r magic(3), magi(5)" >& test.txt
New features and changes introduced in Version 7.3 (R2006b) are described here.
M-Lint preferences now appear on a new M-Lint panel. There are new M-Lint preferences to disable specific messages or categories of messages, as well as to save the settings for use in a later session. In addition, you can choose to show or hide messages for the MATLAB® Compiler™ product if the MATLAB Compiler product is installed. These new M-Lint preferences apply to the M-Lint code analyzer operating automatically in the Editor/Debugger as well as to the M-Lint Code Check Report you run via the Current Directory browser Directory Reports or Tools > M-Lint > Show M-Lint Report.
Compatibility Considerations. M-Lint preferences were previously accessed via the Editor/Debugger Language settings for M.
When you have multiple documents open within a tool, such as M-files in the Editor/Debugger, select File > Close to readily close selected files in that tool. Alternatively, right-click the document bar to close all open documents or all open documents except the selected document in that tool.
Accessibility features and assistive technologies are now part of the Desktop documentation. In prior versions, they were documented in the general Release Notes.
MATLAB has a new look and feel on the Linux operating system from Linus Torvalds and the Sun Microsystems Solaris operating system that affects windows, decorations, color schemes, and responsiveness of the interface in MATLAB.
Compatibility Considerations. All of the changes are cosmetic, except for file dialog boxes, like Open file. The new file dialog boxes are more conventional and easier to use than in previous versions, and there is no loss in functionality.
When MATLAB finds an info.xml file on the search path or in the current directory, it assumes the file is intended to add information to the Start button or the Help browser, and automatically validates the file against the supported schema. If there is an invalid construct in the info.xml file, MATLAB displays an error in the Command Window. The error is typically of the form
XML-file failed validation against schema located in ... XML-file name: full path to...\info.xml
and might appear when you start MATLAB, press the Start button, or in other situations. For more information about the error and how to eliminate it, see Adding Your Own Toolboxes to the Start Button.
Compatibility Considerations. In previous versions, MATLAB displayed a warning when it encountered an invalid info.xml file.
New features and changes introduced in Version 7.3 (R2006b) are described here.
These improvements were made to the Help browser search feature. Note that they are not supported on Japanese systems.
Search Field Always Shown — The Search for field is now always in view when the Help browser is open. The list of pages found appears in the Search Results tab.
Exact Phrase Searches for More Relevant Results — Find an exact phrase by typing quotation marks around the search term. For example, "plot tools" finds only pages that include plot tools together, but does not find pages that include plot in one part of the page and tools in another part of the page. You can specify more than one exact phrase in a search term, such as "plot tools" "figure pallette".
Wildcards (*) in Search Terms for Variations of a Word (Partial Word Search) — Use the wildcard character (*) in place of letters or digits in your search terms. For example, plot* finds various forms of the word plot, such as plot, plots, and plotting, while p*t find those variations as well as variations of print and part, among others. You can use multiple wildcards in a word or search term.
Boolean Operator Evaluation Order Changed — Boolean NOT operators in search terms are now evaluated first, followed by ORs, and then ANDs. In prior versions, Boolean operators were evaluated in left to right order.
Compatibility Considerations. The search enhancements were facilitated by changing to a new type of database. As a result, any existing Help search databases for non-Mathworks products will not work in R2006b and beyond. The documentation still displays in the Help browser, but it is not included in searches.
If you use Help browser documentation for non-MathWorks products with a pre-R2006b search database, a message will display in the Help browser to notify you that the documentation will not be included in searches. If you want search to work for that documentation, contact the product provider to request an R2006b-compatible search database.
If you provide documentation for the Help browser and want the documentation to be included in the searches, you need to update the helpsearch.db entry in the info.xml file to the helpsearch directory, and prepare an R2006b-compatible help search database. This process is much easier than in the past. For instructions, contact Technical Support.
New features and changes introduced in Version 7.3 (R2006b) are described here.
The Workspace browser includes new columns that automatically display results of common statistical calculations: Minimum, Maximum, Range, Mean, Median, Mode, Variance, and Standard Deviation. Use View > Choose Columns to specify the columns to show.
See also File > Preferences > Workspace for associated preferences.
You can open larger arrays in the Array Editor. In previous versions, large arrays would fail to open in the Array Editor.
New features and changes introduced in Version 7.3 (R2006b) are
Use the new File Comparisons tool to highlight the differences between two files. Open a file, select Tools > Compare Against, and then browse to select the second file or drag it into the tool from the Current Directory browser or Windows Explorer. The two files appear aligned in a window with highlights and indicators for any lines that differ, as shown in this example. For more information, see Comparing Files and Folders.
Use elements in the toolbar to exchange the left-right positions of the two files and to specify the number of columns shown.
You can also run the File Comparisons tool from the desktop by selecting Desktop > File Comparisons. Drag a file from the Current Directory browser or Windows Explorer into the tool. Then drag the second file into the tool.
These are the new features and changes to M-Lint:
General Enhancements—Japanese Messages, and Line Number in Indicator Bar.
On Japanese systems, messages now appear in Japanese.
The messages that appear at the indicator bar now includes the line number.
Suppressing M-Lint Messages. The M-Lint automatic code analyzer in the Editor/Debugger now provides a few ways for you to suppress specific messages and categories of messages:
Ignore Specific Instance — Right-click at the underline for an M-Lint message, and from the context menu, suppress just that instance. M-Lint adds %#ok and a new message ID tag to the end of the line, which is the syntax in MATLAB for suppressing an M-Lint message.
Disable All Instances — Right-click at the underline for an M-Lint message, and from the context menu, disable all instances of that message in all files. This changes the preference setting for that message.
Use Preferences to Disable All Instances — Select File > Preferences > M-Lint, and disable specific messages or categories of messages, which applies to all instances in all files. You can save the settings to an M-Lint preference file. From the Editor/Debugger, you can select the M-Lint preference file from the Tools > M-Lint menu.
The M-Lint Code Check report also uses the preferences and suppresses the display of specific messages and categories of messages, per the preference settings.
Deployment Messages in M-Lint. M-Lint now displays deployment messages for the MATLAB Compiler product, such as MCC does not permit the CD function, which appear if the MATLAB Compiler product is installed and you select the M-Lint preference to Show MATLAB Compiler deployment messages. You can also disable or enable all deployment messages via the Editor/Debugger Tools > M-Lint menu. You can suppress specific messages using the same methods as for other M-Lint messages.
Compatibility Considerations. M-Lint preferences were previously accessed via the Editor/Debugger Language settings for M. See also mlint Message IDs Changed and %#ok Syntax Enhanced
You can save the status of breakpoints to a MAT-file using s=dbstatus and restore the breakpoint status at a later time by loading the MAT-file using the new dbstop(s) option. For example, set breakpoints in collatz. Run s=dbstatus to assign the breakpoint status to s; use the 'completenames' option to save absolute pathnames and breakpoint function nesting sequence. Save s to a MAT-file by running, for example, save mydebugsession s. At a later time, run load mydebugsession to restore s, and then run dbstop(s) to restore the breakpoints.
If you debug multiple files at once, you can exit debug mode for all files by running dbquit('all'). If you debug file1 and step into file2, running dbquit terminates debugging for both files. However, if you debug file3 and also debug file4, running dbquit terminates debugging for file4, but file3 remains in debug mode until you run dbquit again. The new dbquit('all') option ends debugging for both file3 and file4, and as dbquit does, ends debugging for file1 and file2.
New features and changes introduced in Version 7.3 (R2006b) are described here.
The File Comparison Report, one of the directory reports available in the Current Directory browser, was removed.
Compatibility Considerations. The new File Comparisons tool replaces the File Comparison Report. The tool provides the same functionality as the report did, and adds new features. For details, see File Comparisons Tool Added.
You can indicate specific messages or categories of messages you want M-Lint to report. For details, see M-Lint Enhancements for Suppressing Messages, and Showing Messages for the MATLAB Compiler Product.
Compatibility Considerations. In previous versions, the M-Lint Code Check report showed all messages except those suppressed via a %#ok at the end of a line. Now, the M-Lint Code Check report will show only the messages that are enabled via M-Lint preferences.
The mlint function with the -id option returns message IDs using a new form. For example, when you run
mlint('filename.m', '-id')MATLAB Version 7.2 (R2006a) returns
L 22 (C 1-9) 2:AssignmentNotUsed : The value ...
whereas MATLAB Version 7.3 (R2006b) returns
L 22 (C 1-9): NASGU: The value ...
The %#ok syntax used in M-files to suppress the display of M-Lint messages for a line has been enhanced to support multiple messages per line. For example, given this line in an M-file,
data{nd} = getfield(flds,fdata{nd});two M-Lint messages result:
34: 'data' might be growing inside a loop; ... consider preallocating for speed.
34: Use dynamic fieldnames with structures instead of GETFIELD... Type 'doc struct' for more information.
In MATLAB Version 7.2 (R2006a), M-Lint messages could only be suppressed for the entire line:
data{nd} = getfield(flds,fdata{nd}); %#okIn MATLAB Version 7.3 (R2006b), you can still use %#ok to suppress all messages for the line, or you can add an ID tag to indicate the exact messages to suppress. For example, this suppresses only the first message about data growing inside a loop:
data{nd} = getfield(flds,fdata{nd}); %#ok<GFLD>To suppress more than one message per line, separate the ID tags with a comma. For example, this suppresses both messages:
data{nd} = getfield(flds,fdata{nd}); %#ok<GFLD,AGROW>Compatibility Considerations. In previous versions, the message IDs returned from mlint with the -id option, were of a form that included a numeric identifier, followed by the category. If you rely on the exact ID values, you will need to make modifications to use the new form.
If you use M-Lint in MATLAB Version 7.3 (R2006b) and then run those files a previous version, M-Lint in the previous version ignores the tag and IDs that follow the %#ok, and therefore suppresses all messages for that line, which is the expected behavior for the previous version.
The mlintrpt function now accepts a new option that applies the preferences saved to an M-Lint settings file. It works with the file or dir syntax:
mlintrpt('fullpath_to_file', 'file', 'fullpath_to_configfile.txt')
mlintrpt('fullpath_to_dir', 'dir', 'fullpath_to_configfile.txt')For example, create the file NoSemiSetting.txt by saving settings in File > Preferences > M-Lint. Later, use the settings via preferences or M-Lint in the Editor/Debugger, or via mlintrpt as in this example:
mlintrpt('lengthofline.m', 'file', 'I:\MATLABFiles\NoSemiSettings.txt')which displays an M-Lint report in the MATLAB Web browser for the lengthofline file in the current directory using the M-Lint settings in I:\MATLABFiles\NoSemiSettings.txt.
The Profiler included a refresh button
on the toolbar. This
button has been removed. It performed an action similar to the Refresh button
that appears in many of the Profiler reports, so use that button instead.
In MATLAB 7.1 (R14SP3), the notebook function was enhanced to automatically detect the version of the Microsoft Word application and other required information. This feature changed the notebook -setup syntax—arguments to specify the version of the Microsoft Word application (wordversion, wordlocation, templatelocation) were no longer supported. If you used those arguments, MATLAB ignored them and issued a warning. Now in MATLAB 7.3 (R2006b), if you use those arguments, MATLAB errors.
Compatibility Considerations. If you use notebook with the wordversion, wordlocation, and templatelocation arguments in any of your files (for example, startup.m), remove them to prevent errors.
 | Version 7.3 (R2006b) MATLAB Software | Mathematics, MATLAB Version 7.3 (R2006b) |  |
Includes the most popular MATLAB recorded presentations with Q&A sessions led by MATLAB experts.
| © 1984-2009- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
