| Using function after .reset [message #82652] |
Thu, 10 January 2013 09:47  |
PMan
Messages: 61
Registered: January 2011
|
Member |
|
|
Hi
I am running IDL 8.2.1 on a Linux 64 bit system. I have encountered an odd problem using a function after a .reset is performed.
Upon opening idlde, I run my program without a problem. I decide I need make a change in an object and in order to recompile the object with the change I must .reset. I rerun the program and everything must recompile. One function (called imgOpen with filename imgopen.pro) which compiled and ran fine in the first run, now compiles, but the function cannot be found. See below:
% Compiled module: IMGOPEN.
% Attempt to call undefined procedure/function: 'IMGOPEN'.
Anyone have an idea why this occurs?
Thanks.
|
|
|
|
|
|
| Re: Using function after .reset [message #82746 is a reply to message #82652] |
Thu, 10 January 2013 10:32  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Paul Mallas writes:
> I use "compile_opt idl2" often and it is indeed used in the function that can't be found. But I will look around.
Coyote is always telling me to play the percentages when it comes to
women, tennis, and gambling. Bad advice, as always. :-(
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thue. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: Using function after .reset [message #82747 is a reply to message #82652] |
Thu, 10 January 2013 10:16 |
PMan
Messages: 61
Registered: January 2011
|
Member |
|
|
On Thursday, January 10, 2013 1:11:10 PM UTC-5, David Fanning wrote:
> Paul Mallas writes:
>
>
>
>> I am running IDL 8.2.1 on a Linux 64 bit system. I have encountered an odd problem using a function after a .reset is performed.
>
>>
>
>> Upon opening idlde, I run my program without a problem. I decide I need make a change in an object and in order to recompile the object with the change I must .reset. I rerun the program and everything must recompile. One function (called imgOpen with filename imgopen.pro) which compiled and ran fine in the first run, now compiles, but the function cannot be found. See below:
>
>>
>
>> % Compiled module: IMGOPEN.
>
>> % Attempt to call undefined procedure/function: 'IMGOPEN'.
>
>>
>
>> Anyone have an idea why this occurs?
>
>
>
> I don't know this for a fact, and I'm guessing because I haven't been
>
> following this thread closely, but I would wager some serious money that
>
> if you stuck Compile_Opt idl2 in all of your program modules and
>
> restarted IDL, that this problem would go away.
>
>
>
> In fact, I'm going to double down on it! ;-)
>
>
>
> Cheers,
>
>
>
> David
>
>
>
>
>
>
>
> --
>
> David Fanning, Ph.D.
>
> Fanning Software Consulting, Inc.
>
> Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
>
> Sepore ma de ni thue. ("Perhaps thou speakest truth.")
I use "compile_opt idl2" often and it is indeed used in the function that can't be found. But I will look around.
|
|
|
|
| Re: Using function after .reset [message #82748 is a reply to message #82652] |
Thu, 10 January 2013 10:11 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Paul Mallas writes:
> I am running IDL 8.2.1 on a Linux 64 bit system. I have encountered an odd problem using a function after a .reset is performed.
>
> Upon opening idlde, I run my program without a problem. I decide I need make a change in an object and in order to recompile the object with the change I must .reset. I rerun the program and everything must recompile. One function (called imgOpen with filename imgopen.pro) which compiled and ran fine in the first run, now compiles, but the function cannot be found. See below:
>
> % Compiled module: IMGOPEN.
> % Attempt to call undefined procedure/function: 'IMGOPEN'.
>
> Anyone have an idea why this occurs?
I don't know this for a fact, and I'm guessing because I haven't been
following this thread closely, but I would wager some serious money that
if you stuck Compile_Opt idl2 in all of your program modules and
restarted IDL, that this problem would go away.
In fact, I'm going to double down on it! ;-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thue. ("Perhaps thou speakest truth.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
