Re: Correct format of "included" files (using "at" sign) [message #1850 is a reply to message #1848] |
Tue, 01 March 1994 11:30  |
kspencer
Messages: 21 Registered: December 1993
|
Junior Member |
|
|
steele@wesson.phys.ucalgary.ca (Dave Steele) writes:
> I'm trying to use the "at" sign (the $%^&*! 'xrn' editor won't let
> me type it!) to substitute some code into IDL. The procedure is
> tersely described on p. 2-7 of the User's Guide for v3.1. I'm
> getting a problem that I think has to do with the format of the
> code I'm including. It is an IF_THEN_ELSE block with no header
> line (like PRO ... or FUNCTION ...) and no trailer lines (like
> RETURN, END, EXIT). If I run the routine that invokes the code
> substitution, I get syntax errors in the first lines following the
> invocation. If I add a line saying 'END' to the substituted code,
> I get dropped back to the IDL> prompt at the end of the substituted
> code.
[deleted]
> Dave
> --
> David Steele | Internet : steele@wesson.phys.ucalgary.ca
> Department of Physics and Astronomy | SPAN : CANCAL::STEELE
> The University of Calgary | Phone : +1 403 220 8651
> OPINIONS EXPRESSED WITHIN ARE MY OWN AND NOT THOSE OF THE UNIVERSITY OF CALGARY
Dave,
Yes, it's frustrating that they don't document the differences in syntax
between compiled routines and the "script" files. As far as I know, you
have to keep statements to one line, and can't use block statements. IDL
just treats the commands as if they were issued in interactive mode.
Kevin
-----------------------------------------------------------
Kevin Spencer
Cognitive Psychophysiology Laboratory and Beckman Institute
University of Illinois at Urbana-Champaign
kspencer@p300.cpl.uiuc.edu / kspencer@psych.uiuc.edu
-----------------------------------------------------------
|
|
|