MATLAB Release Notes |
|
External Interfaces/API Issues
Concatenation of Java Objects
When you concatenate Java objects, the class of the resultant object depends on the classes of the input objects, as follows:
If the input objects are of the same class, MATLAB makes the output object of that class. This was true in Version 6.0 as well.
- If the input objects are of different classes, but all inherit from a common class, MATLAB makes the output object of the common parent class. MATLAB selects the lowest common parent in the Java class hierarchy as the output class. This is new behavior for Version 6.1.
- For example, concatenating objects of classes
java.lang.Integer
and java.lang.Double
creates a new object of class java.lang.Number
.
- If the input objects are of different and unrelated classes, then MATLAB makes the output object of the
java.lang.Object
class. This was true in Version 6.0 as well.
Obsolete Fortran MX, MEX, MAT, and ENG Functions
The following Fortran MX, MEX, MAT, and ENG functions are considered to be obsolete as of Version 6.1. Support for these functions may be removed from a future MATLAB release.
Table 2-5: Obsolete Fortran MX Functions
mxCreateFull
|
mxFreeMatrix
|
mxIsFull
|
mxIsString
|
Table 2-6: Obsolete Fortran MEX Functions
mexGetEps
|
mexGetGlobal
|
mexGetFull
|
mexGetInf
|
mexGetMatrix
|
mexGetMatrixPtr
|
mexGetNaN
|
mexIsFinite
|
mexIsInf
|
mexIsNaN
|
mexPutFull
|
mexPutMatrix
|
Table 2-7: Obsolete Fortran MAT Functions
matDeleteMatrix
|
matGetFull
|
matGetMatrix
|
matGetNextMatrix
|
matGetString
|
matPutFull
|
matPutMatrix
|
matPutString
|
Table 2-8: Obsolete Fortran Engine Functions
engGetFull
|
engGetMatrix
|
engPutFull
|
engPutMatrix
|
| Graphics Issue | | Known Software and Documentation Problems | |