The features described in this topic are obsolete
and should not be used in new IDL code.

ITRESOLVE

Syntax | Arguments | Keywords | Examples | Version History | See Also

The ITRESOLVE procedure resolves all IDL code within the iTools directory, as well as all other IDL code required for the iTools framework. This procedure is useful for constructing SAVE files containing user code that requires the iTools framework.

This routine is written in the IDL language. Its source code can be found in the file itresolve.pro in the lib/itools subdirectory of the IDL distribution.

Syntax

ITRESOLVE [, PATH=string]

Arguments

None.

Keywords

PATH

Set this keyword to a string containing the full path to the iTools directory. The default is to use the lib/itools subdirectory within which the ITRESOLVE procedure resides.

Examples

Example 1

Suppose you wish to create a SAVE file that contains all of the code necessary to run an iTool you have created with the name mytool. First, start with a clean IDL session and compile all of your own code:

.COMPILE mytool 

Now compile all of the iTools code:

ITRESOLVE 

Finally, create the SAVE file:

SAVE, FILE='mytool.sav', /ROUTINES, /COMPRESS 

Example 2

Since ITRESOLVE calls RESOLVE_ALL, it will attempt to include all routines required by any already-compiled routine. This may cause problems if your application calls routines that are already contained in a different SAVE file, but you do not want the routines from the other SAVE file to be included within your own iTools SAVE file. In this case, resolve your routines in two steps:

First, start with a clean IDL session and compile all of the iTools code:

ITRESOLVE 

Next, compile your own application:

.COMPILE mytool2 

Then, resolve all of your required routines, skipping any that you do not want included:

RESOLVE_ALL, SKIP_ROUTINES=routines_that_should_not_be_resolved 

Finally, create the SAVE file:

SAVE, FILE='mytool2.sav', /ROUTINES, /COMPRESS 

Version History