| behavior of .CONTINUE executive command, in IDLWAVE [message #92399] |
Tue, 08 December 2015 09:44 |
MarioIncandenza
Messages: 231
Registered: February 2005
|
Senior Member |
|
|
Hello IDL wizards,
I continue to use IDL in an Emacs window with the IDLWAVE IDE. I had the following unexpected experience: I was running a program interactively and found there was a correctable mistake in a routine. So:
IDL>.run my_program.pro
% Error: YOU SUCK
IDL>var='variable now set, my bad.'
IDL>.CONTINUE
And away we went. But since the mistake was in a routine called multiple times in a loop, it happened again:
% Error: YOU SUCK
IDL>var='variable now set, my bad.'
IDL>.CONTINUE
At that point, simply wanting the routine to run to completion without restarting, I dumped a series of lines into the IDLWAVE buffer, by typing them and hitting <ENTER>:
var='variable now set, my bad.'<ENTER>
.CONTINUE<ENTER>
And then I went for coffee.
When I came back, I found that the job had correctly .CONTINUE'd through the entire loop. Then it finished its job. And *THEN*, after the compiled program had reached its END, the next .CONTINUE from the command line caused the program to RESTART from the top.
Has anyone ever witnessed this behavior from .CONTINUE?
Happy holidays to all,
--Edward H.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
