Custom Query (27 matches)

Now IDLWAVE menu in Emacs provide old fashion header (see Templates/Doc? Header (C-c C-h)). It will be great to change this template with IDLdoc syntax.

Diagnostics of wrong calling sequence of xfile might be more explicit to help debug.

Here are some examples :

IDL> xfile,fdsfds
% Compiled module: XFILE.
% Compiled module: REPORT.
% Compiled module: STR_SEP.
% Compiled module: ROUTINE_NAME.
% L.39 /Users/fplod/SAXO_DIR_ws/SRC/Utilities/xfile.pro: Input parameter must be a string and not a UNDEFINED

No release, no reminder of the call.

Something like that

% L.39 /Users/smasson/SAXO_RD/SRC/Utilities/xfile.pro rev239:
Input parameter of xfile was : fdsfds
Input parameter must be a file.

may ease debug.

IDL>  xfile 
% L.39 /Users/fplod/SAXO_DIR_ws/SRC/Utilities/xfile.pro: Input parameter must be a string and not a UNDEFINED

should be replaced by

% L.39 /Users/smasson/SAXO_RD/SRC/Utilities/xfile.pro rev239:
No input parameter for xfile.
Input parameter must be a file.

IDL>  xfile, 'dqsdqs'
% Compiled module: XDISPLAYFILE.
% Compiled module: XMANAGER.
IDL> }}}

no error is written after IDL prompt. A window "NOT FOUND" opens with the following message 
{{{
FILE_LINES: Error opening file. File: NOT FOUND
 Unable to display NOT FOUND
}}}

This window is useless. Message should be written after the prompt like this for example :
{{{
% L.39 /Users/smasson/SAXO_RD/SRC/Utilities/xfile.pro rev239:
Input parameter of xfile was : 'dqsdqs'
Input parameter must be a file.
}}}

for changeset:272 commiter (Seb)

As you add a keyword in the calling sequence of ncdf_getmask in changeset:272, you should add at the same time documentation about it in the header of this file :

 ; @keyword INVMASK {type=++}
 ; description and usage

May be you can also change examples according to this modification.

For example, is this one still available (no INVMASK in this call) ?

IDL> mask = ncdf_getmask('meshmaskORCA2.nc', maskname = 'tmask')

or you can add a new example using this new keyword ...

Sorry I don't not yet if {required} or {optional} can be added in a keyword definition in the header ... I'll check.