User`s guide

R2009b
12-4
Compatibility Considerations
In previous releases, if you entered the latitude limits of the 'MapLatLimit' property
in descending order when using axesm or setm, you could end up with a map axes that
was internally inconsistent, possibly resulting in unexpected errors during subsequent
operations. This is no longer the case.
Second Input Argument of roundn No Longer Supports Complex
Numbers, Non-integers, or Default Values
roundn no longer accepts certain types of input for the second input argument, N, which
is supposed to be a real, integer-valued exponent. Now, if you use a complex number or
non-integer as the second input to roundn, you will receive an error; and if you omit N,
you will receive a warning. You will also receive an error if you call roundn with a second
output argument to capture error message strings.
Compatibility Considerations
In previous releases, if you used a complex number or non-integer as the second input to
roundn, this number would be converted into a real integer. If you called roundn with a
second output argument to capture error message strings, you would receive an obsolete
syntax warning.
In R2009b, -2 is still the default value for the second input argument. This default
is being phased out, however, and in the future you will receive an error if you fail to
supply the second input argument. If there are any instances in your code with the usage
roundn(x), you should replace them with roundn(x,-2).
The two-output syntax option was previously deprecated and has resulted in a warning
in the past several releases.
Functions Removed
Functions Being Removed in a Future Release
Name Stage Compatibility Considerations
colorui Still
runs
Replace all existing instances of colorui with uisetcolor.