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:
MEX-Files Calling BLAS or LAPACK Functions Must Be Updated On 64-Bit Platforms
Run-Time Libraries Required for Applications Built with Microsoft Visual Studio 2008 Compiler
The interface to .NET allows you to bring .NET assemblies into the MATLAB environment, to construct objects from classes contained in the assemblies, and to call methods on these objects. For complete documentation of this feature, see MATLAB Interface to .NET Framework. For an overview of the .NET interface, watch this video demo.
MATLAB Serial Port is now supported on the following platforms:
Microsoft Windows 64-bit
Apple Macintosh OS X
Macintosh OS X 64-bit
Linux
Linux 64-bit
Sun Solaris™ 64-bit
MATLAB Version 7.8 (R2009a) supports these new compilers for building MEX-files:
Microsoft Windows (64- and 32-bit) Platforms.
Microsoft Visual Studio 2008 SP1
Linux (64- and 32-bit) Platforms.
gcc Version 4.2.3
Apple Macintosh (32-bit) Platforms.
GNU gfortran Version 4.2.2
The following compilers are supported in Version 7.8 (R2009a), but will not be supported in a future version of MATLAB:
Intel Visual Fortran Version 9.1
Intel Visual Fortran Version 10.1
Intel C/C++ Version 9.1
Microsoft Visual Studio .NET Version 7.1
Intel Visual Fortran Version 9.1
Intel Visual Fortran Version 10.1
Intel C/C++ Version 9.1
Solaris SPARC (64-bit) Platforms.
Sun Studio 11 cc / CC Version 5.8
Sun Studio 11 f90 Version 8.2
MATLAB no longer supports the following compilers:
Open Watcom Version 1.3
Microsoft Visual Studio 2005 Express Edition
Microsoft Platform SDK
Apple Macintosh (32-bit) Platforms.
g95 Version 0.90
Compatibility Considerations. To ensure continued support for building your C/C++ programs, consider upgrading to another supported compiler. For an up-to-date list of supported compilers, see the Supported and Compatible Compilers Web page.
It is improper to call mxFree on an mxArray. Previously, to remedy misleading statements in older documentation, under limited circumstances, MATLAB issued a warning in code that made this error. MATLAB no longer issues the warning.
The correct function to use to release memory for an mxArray is mxDestroyArray. Calling mxFree on an mxArray could cause memory corruption, which might result in a segmentation violation.
MATLAB does not support the -V5 option to the mex function.
You are no longer able to build a MEX-file using the MATLAB Version 5 API. If you use any of the functions shown in the Obsolete Functions: MX Array Manipulation table, you must replace them with functions from the Replacement column, if available. These obsolete functions were deprecated when MATLAB Version 6 was released over 5 years ago.
You must update any MEX-file that calls functions in the BLAS or LAPACK math packages on 64-bit platforms. The change occurs as a result of updated support, described in 64-bit Support in LAPACK and BLAS. Existing MEX-files generated in previous versions of MATLAB will result in undefined behavior (likely crashes), if run in R2009a. The previous versions pass 32-bit integer arguments, but the math routines now read and write to 64 bits of memory. The results you see depend on what is stored in the subsequent 32 bits of memory.
On 64-bit platforms, you must use 64-bit integers for all input and output variables when calling LAPACK and BLAS routines in C and Fortran source MEX-files. Use the mwSignedIndex type for platform-independent code.
MATLAB saves object .o files when compiling MEX-files on Apple Mac OS® Version 10.5 systems so that you can use source-level debugging.
If you distribute a MEX-file, an engine application, or a MAT-file application built with the Visual Studio 2008 compiler, you must provide the Visual C++ run-time libraries. These files are required to run applications developed with Visual C++ on a computer that does not have Visual C++ 2008 installed. For information on locating the Microsoft Visual C++ 2008 Redistributable Package (x86), containing vcredist_x86.exe and vcredist_x64.exe, consult your Microsoft documentation.
It is now possible to use the char** return value and to increment the resulting pointer to retrieve all values. See Passing an Array of Strings.
Added support for accessing values exported by a library.
All fully and partly sized arrays should now work.
Use the following new functions to work with Sun Java objects on the Event Dispatch Thread (EDT).
| Function | Description |
|---|---|
| javaObjectEDT | Construct Java object on EDT |
| javaMethodEDT | Call Java method from EDT |
The underlying technology used in the createClassFromWsdl and parseSoapResponse functions was modified to better ensure support for WSDL and SOAP standards.
There was no intended change to functionality or results of the createClassFromWsdl and parseSoapResponse functions, which The MathWorks verified through testing. There are many variations among WSDL files and Web services and they cannot all be tested. Therefore, it is possible that your results using the createClassFromWsdl and parseSoapResponse functions in this version could differ from a previous version.
Ensure that your results using createClassFromWsdl and parseSoapResponse functions are as expected.
 | Creating Graphical User Interfaces (GUIs), MATLAB Version 7.8 (R2009a) | Version 7.7 (R2008b) MATLAB Software |  |
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 |
