| Re: Error compiling procedure already compiled [message #34393 is a reply to message #34355] |
Mon, 10 March 2003 10:44   |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Fri, 07 Mar 2003 18:16:54 -0700, Rob wrote:
> JD Smith <jdsmith@as.arizona.edu> wrote:
>
>> On Wed, 05 Mar 2003 19:34:01 -0700, Rob wrote:
>>
>>> JD Smith <jdsmith@as.arizona.edu> wrote:
>>>
>>>> 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
>>>
>>> Thanks for the tips, JD. Before I started I installed IDLWAVE 4.1.6
>>> from www.idlwave.org.
>>>
>>> In response to 1. above, is 4.1.6 the the latest version? I've seen
>>> reference to a version 4.6, but I didn't see anything later than
>>> 4.1.6 on the website. Also, strangely, I don't see a Debug->Show
>>> Commands->Everything option in my Debug menu???
>>>
>>>
>> It's actually 4.16 (>4.6). I only use a single decimal. Make sure
>> that's what's actually running by checking the *Messages* log. If you
>> didn't do the install correctly, it may be defaulting to the bundled
>> version. You need to have the shell running for Everything to show,
>> otherwise, you'll just see "Start Shell" or some such. Start it and
>> see. If not, you're probably defaulting to the old version (4.7?).
>>
>>> In response to 3, I haven't changed my IDL prompt, don't even know
>>> how yet...and I'm not using ENVI.
>>>
>>> I'm using IDL 5.6 on OS X with the Aqua version of Emacs 21.3.50.6
>>> and am using Apples latest beta X11 version 0.2.1(Xfree86 4.2.1).
>>> Below is my .emacs and .tcshrc. If you can think of anything to try
>>> I'd really appreciate it!
>>
>> The next release of IDLWAVE will be fully qualified for OSX. Many have
>> gotten it working in the meantime, and I've never heard of an error
>> like this, but I've yet to test it myself. The error output showing
>> "Everything" will be definitive.
>>
>>> .Emacs file:
>>
>> No setting here should cause these problems.
>>
>
> The messages log confirms I'm running 4.16. But still, under my Debug
> menu I have, in order, Compile and Run, Breakpoints, Continue/Step,
> Examine Expressions, Call Stack, Update Working Directory, Reset IDL
> toggle Toolbar, and Exit IDL. That's it. The IDL shell is running. I
> don't have a Show Commands in my Debug menu. Am I looking in the wrong
> place?
Sorry about that Rob... it's been long enough since the last release
that I'm beginning to forgot things I put in afterwards, and this menu
was one of them. The functionality is there, just not in a menu. You
can set it via customize: IDLWAVE -> Customize -> Browse IDLWAVE
Group; Idlwave Shell Command Setup -> Idlwave Shell Show Commands.
Set that to "everything", save for current session, and give another
try.
JD
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
