User`s guide

15-9
• unitstr
• utmzone
• utmzoneui
For example, even with no map axes present, the command
[mstruct, msg] = gcm
returned without error in R2007b and earlier, but placed an error message string in msg.
These syntaxes have been disabled in R2008a. If you try to use them, a warning is
issued. The warning may be followed by an error, depending on whether or not an error
condition is encountered within the function. For example, if a map axes is present, the
command above results in
Warning: Function GCM no longer returns error message strings in
output argument MSG. Instead any errors are thrown where they occur.
You should remove the last output argument (MSG) from your call to
GCM in order to avoid this warning. If you want to handle errors
yourself, call GCM in a try-catch block.
> In mapdisp/private/warnObsoleteMSGSyntax at 6
In gcm at 20
If there is no map axes, it results in
Warning: Function GCM no longer returns error message strings in
output argument MSG. Instead any errors are thrown where they occur.
You should remove the last output argument (MSG) from your call to
GCM in order to avoid this warning. If you want to handle errors
yourself, call GCM in a try-catch block.
> In mapdisp/private/warnObsoleteMSGSyntax at 6
In gcm at 20
??? Error using ==> gcm>checkaxes at 41
No axes in current figure.
Select a figure with map axes or use AXESM to define one.
Error in ==> gcm at 24
h = checkaxes(varargin{:});
Compatibility Considerations
As suggested by this warning, if you have any scripts or functions of your own that
depend on the old syntax, you should remove the msg argument and place the function
call in a try-catch block instead.