comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Compile or not compile?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Compile or not compile? [message #43149 is a reply to message #42879] Mon, 21 March 2005 11:47 Go to previous messageGo to previous message
K. Bowman is currently offline  K. Bowman
Messages: 330
Registered: May 2000
Senior Member
In article <pan.2005.03.21.16.40.40.173850@as.arizona.edu>,
JD Smith <jdsmith@as.arizona.edu> wrote:

> The other thing to note is that the PATH is not cached on startup,
> only after the first time it is read. So try something like:
>
> IDL> .run file_in_my_path
>
> create another_file_in_my_path.pro in the same location as
> file_in_my_path.pro
>
> IDL> .run another_file_in_my_path.pro
>
> This will fail if the paths are cached.

In my experience (OS X), creating a new program file after starting IDL
gives the following behavior (file names appropriated from above):

IDL> file_in_my_path
% Compiled module: FILE_IN_MY_PATH.

Then create a new program file

IDL> another_file_in_my_path
% Attempt to call undefined procedure/function:
'ANOTHER_FILE_IN_MY_PATH'.
% Execution halted at: $MAIN$
IDL> .r another_file_in_my_path
% Compiled module:.ANOTHER_FILE_IN_MY_PATH

So, automatic compilation does not work, but manual compilation does. I
still don't understand that.

Ken Bowman
[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: IRIG Time Stamp to Julday
Next Topic: (",) Do You Want To Know For Sure You Are Going To Heaven?

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Mon Dec 01 03:36:26 PST 2025

Total time taken to generate the page: 1.52552 seconds