Re: IDL error message [message #44470] |
Thu, 16 June 2005 07:17 |
jiajianshen
Messages: 4 Registered: June 2005
|
Junior Member |
|
|
Thanks a lot!
I find the problem and as you pointed out, I need reset the path for
the functions to run properly.
Jiajian
Mark Hadfield <m.hadfield@niwa.co.nz> wrote in message news:<d8qv70$vq5$1@newsreader.mailgate.org>...
> jiajian shen wrote:
>> Hi All,
>>
>> I had a problem in running IDL that I got error messages in compiling
>> the code even the code has nothing wrong.
>>
>> I knew the code is non-error because it really works well a few
>> minutes ago. However, if I stopped the code forcedly when it's still
>> running, the same code gave me the error message in compiling. After
>> logging out the IDL or even log out the computer, the situation still
>> keeps.
>>
>> I don't why this happens because the code is exactly the same. Will
>> this because of my forced stopping the code running? If so, how can I
>> fix it up?
>
> When you stopped the code running, did IDL open the source code file in
> its editor at the line where you interrupted it? Perhaps you
> inadvertently modified the code by pressing a key then.
>
> Perhaps there are references in the code to functions that are not on
> the !PATH. IDL might accept these if the functions have already been
> compiled manually, but not when it's restarted.
>
> You might want to look closely at the compile error messages and the
> lines that seem to trigger them. If they don't make sense to you, you
> could post them here.
|
|
|
Re: IDL error message [message #44474 is a reply to message #44470] |
Wed, 15 June 2005 21:29  |
Mark Hadfield
Messages: 783 Registered: May 1995
|
Senior Member |
|
|
jiajian shen wrote:
> Hi All,
>
> I had a problem in running IDL that I got error messages in compiling
> the code even the code has nothing wrong.
>
> I knew the code is non-error because it really works well a few
> minutes ago. However, if I stopped the code forcedly when it's still
> running, the same code gave me the error message in compiling. After
> logging out the IDL or even log out the computer, the situation still
> keeps.
>
> I don't why this happens because the code is exactly the same. Will
> this because of my forced stopping the code running? If so, how can I
> fix it up?
When you stopped the code running, did IDL open the source code file in
its editor at the line where you interrupted it? Perhaps you
inadvertently modified the code by pressing a key then.
Perhaps there are references in the code to functions that are not on
the !PATH. IDL might accept these if the functions have already been
compiled manually, but not when it's restarted.
You might want to look closely at the compile error messages and the
lines that seem to trigger them. If they don't make sense to you, you
could post them here.
--
Mark Hadfield "Kei puwaha te tai nei, Hoea tahi tatou"
m.hadfield@niwa.co.nz
National Institute for Water and Atmospheric Research (NIWA)
|
|
|