| Re: library help -- multiple procedures in one file [message #30955 is a reply to message #30954] |
Fri, 24 May 2002 09:50   |
Liam E. Gumley
Messages: 378
Registered: January 2000
|
Senior Member |
|
|
David Fanning wrote:
>
> Chris O'Dell (odell@cmb.physics.wisc.edu) writes:
>
>> This question is mostly aimed at people who build libraries for public
>> use (David, Craig, etc). I am putting together a lot of the little
>> useful routines I have written as a grad student into a library, and was
>> wondering, should I juse make EVERY procedure/function have its own
>> file? In PASCAL, I was a big proponent of nested functions;
>> functions/procedures really ONLY used by one other procedure or
>> function. But in IDL, those functions aren't compiled on the fly and
>> you have to open the darn function file and compile them all every time
>> you start idlde. Is there any way around this?
>
> There should never be any reason to manually compile a file in IDL.
[stuff deleted]
I have to say that I manually compile procedures or functions all the
time during development and testing, e.g.
1) Open a source file in nedit (or emacs, vi, IDLDE etc.),
2) Make changes to the file and save it,
3) Recompile the procedure or function (using .compile),
4) Run a test,
5) Go back to step 2 and iterate until it runs correctly.
So it's probably more accurate to say that once you are finished
modifying a source file, and you've placed it in the IDL path, there
should never be a reason to compile it manually.
Cheers,
Liam.
Practical IDL Programming
http://www.gumley.com/
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
