| Re: On-the-fly compilation of routines [message #63405 is a reply to message #63334] |
Thu, 06 November 2008 10:43   |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
gsever writes:
> The routines have been structured like Mr. Bauer said in his first
> reply. I would like to hear your comments about how we can improve the
> organization of our program.
>
> One of my confusion has not been resolved yet. For example on a modern
> embedded C compiler, throughout the debugging process if I make a
> change on the source code and save the file, and try to observe the
> same function by executing a command or function, the compiler warns
> me to re-compile the code. While doing this, it only compiles the
> recently changed file (I mean as far as I understand the compiler or
> linker attaches a file stamp or flag them, so next time it doesn't re-
> compile unchanged files. This means a significant compiling speed
> improvement and this is something I haven't observed in IDL.
No, because it is typically not necessary to every recompile
everything, except when you start IDL. You are working in
the Workbench, so when you finish editing a file, and wish
to re-compile just that file, reach up and click the "Compile"
button. (It looks like a set of gears. Don't ask me.) Just
that one file you are working on gets compiled. On my Windows
machine CNTL-F8 does the same thing.
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.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
