| Re: Error compiling procedure already compiled [message #34335 is a reply to message #34330] |
Wed, 05 March 2003 08:49   |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Tue, 04 Mar 2003 21:14:58 -0700, Rob wrote:
> Okay, so I jumped the gun. Apparently whenever the routine info is
> updated I can no longer compile without recieving the error. The line
> about routine info in my .emacs just caused IDLWAVE to perform the
> updated more frequently, so that's why I thought it was fixed...routine
> info just hadn't been updated yet. Below is another copy of the error
> message. As you can see, after routine info is updated, a temp file is
> written, and following compiling and .run'ing I recieve the Routine Info
> warning. Any suggestions what I can do to fix this?
>
> Scanning all buffers...
> Routine info updated: buffer(3) compiled(0) catalog(591) system(1324)
> Querying the shell
> Wrote /tmp/idltemp19963iX
> Finishing initialization in idle time...done Routine info updated:
> buffer(3) compiled(0) catalog(591) system(1324) (No changes need to be
> saved)
> Routine Info warning: No match for END line in
>>>>
> RESTORE, '/tmp/idltemp1996CFV' & idlwave_routine_info % RESTORE:
> Procedure IDLWAVE_ROUTINE_INFO can't be restored while active. %
> RESTORE: Procedure IDLWAVE_PRINT_INFO_ENTRY can't be restored while
> active.
>>>> BEGIN OF IDLWAVE ROUTINE INFO ("<@>" IS THE SEPARATOR)
> % ROUTINE_INFO: String expression required in this context: NAME. %
> Execution halted at: IDLWAVE_PRINT_INFO_ENTRY % IDLWAVE_ROUTINE_INFO %
> IDLWAVE_PRINT_INFO_ENTRY %
> IDLWAVE_ROUTINE_INFO % $MAIN$
> IDL>
> <<<
>
This is a sign that IDLWAVE is getting out of sync with the IDL
process. It's looking for a terminated block of output to parse, in
this case to learn about all the routines IDL knows about. I can
think of a few possibilities:
1. A read/write lag with comint, the mode which interacts with the IDL
shell. Newer versions of IDLWAVE deal with this a bit better.
2. Something specific to your environment in the output of your
routine_info is confusing IDLWAVE. Seems unlikely, but possible.
3. You've changed your "IDL> " prompt to something else without
telling IDLWAVE about it (e.g. if you're using ENVI).
Can you tell me what version of Emacs, IDL, and IDLWAVE (see
*Messages*) you are using? And, if you can get it to repeat and have
a recent IDLWAVE, check the menu box Debug->Show Commands->Everything,
generate the error, and mail me the dump of info you find in the shell
buffer.
JD
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
