| Re: Trouble finding procedure files [message #53778] |
Mon, 30 April 2007 12:40 |
Ryan.
Messages: 77
Registered: March 2006
|
Member |
|
|
> Did you change the name of the procedure in the file or just change the
> filename? From your first .compile command, it looks like you didn't
> change the name of the procedure.
Thanks Mike, I did forget to change the name of the procedure in the
file. It works fine now.
Ryan.
|
|
|
|
| Re: Trouble finding procedure files [message #53779 is a reply to message #53778] |
Mon, 30 April 2007 08:51  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Ryan. writes:
> I have a procedure that I have modified from an older version that IDL
> cannot seem to find. My old routine was called
> 'gen_wkly_snr_dates.pro' and the new one is called
> 'gen_wkly_snr_dates_v2.pro'. I moved the old procedure out of any of
> the folders in the path to test the new one. This is what happens
> when I attempt to compile it:
>
> IDL> .compile gen_wkly_snr_dates_v2
> % Compiled module: GEN_WKLY_SNR_DATES.
> IDL> gen_wkly_snr_dates_v2
> % Compiled module: GEN_WKLY_SNR_DATES_V2.
> % Attempt to call undefined procedure/function:
> 'GEN_WKLY_SNR_DATES_V2'.
> % Execution halted at: $MAIN$
>
> It compiles the old routine when I want it to compile the new one.
> The new one is in the current working directory. I've tried exiting
> IDL and restarting but I get the same message. What is wrong?
Make sure the name of the procedure is EXACTLY the same
as the name of the file, or you will be wasting all your
time compiling files that don't need to be compiled. :-)
http:/www.dfanning.com/tips/namefiles.html
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: Trouble finding procedure files [message #53780 is a reply to message #53779] |
Mon, 30 April 2007 07:39 |
mchinand
Messages: 66
Registered: September 1996
|
Member |
|
|
In article <1177943153.910600.320130@h2g2000hsg.googlegroups.com>,
Ryan. <rchughes@brutus.uwaterloo.ca> wrote:
> Dear All,
>
> I have a procedure that I have modified from an older version that IDL
> cannot seem to find. My old routine was called
> 'gen_wkly_snr_dates.pro' and the new one is called
> 'gen_wkly_snr_dates_v2.pro'. I moved the old procedure out of any of
> the folders in the path to test the new one. This is what happens
> when I attempt to compile it:
>
> IDL> .compile gen_wkly_snr_dates_v2
> % Compiled module: GEN_WKLY_SNR_DATES.
> IDL> gen_wkly_snr_dates_v2
> % Compiled module: GEN_WKLY_SNR_DATES_V2.
> % Attempt to call undefined procedure/function:
> 'GEN_WKLY_SNR_DATES_V2'.
> % Execution halted at: $MAIN$
>
> It compiles the old routine when I want it to compile the new one.
> The new one is in the current working directory. I've tried exiting
> IDL and restarting but I get the same message. What is wrong?
>
Did you change the name of the procedure in the file or just change the
filename? From your first .compile command, it looks like you didn't
change the name of the procedure.
--Mike
--
Michael Chinander
m-chinander@uchicago.edu
Department of Radiology
University of Chicago
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
