| Re: library help -- multiple procedures in one file [message #30949 is a reply to message #30948] |
Fri, 24 May 2002 11:09   |
![Paul Van Delst[1] is currently offline](theme/default/images/xoffline.png.pagespeed.ic.XRkd1fkXye.png "Paul Van Delst[1] is currently offline")
Paul Van Delst[1]
Messages: 1157
Registered: April 2002
|
Senior Member |
|
|
Chris O'Dell wrote:
>
> 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?
FWIW, I do it the way both Liam and David recommend. Every function procedure in it's own
file. The only time I have more than one function procedure in a file (as far as I can
recall) is for widget code (all the event handlers and what not are listed first) and for
object code (the few, well....one, I have written). And even so, for the widget stuff at
least, you can still have separate files for the event handlers and whatever else is
required. I did that once for a particularly obtuse widget program I wrote (back when it
was still a novelty to do that stuff).
I never use .compile (or whatever) unless I'm actively modifying the file during
development.
paulv
--
Paul van Delst Religious and cultural
CIMSS @ NOAA/NCEP/EMC purity is a fundamentalist
Ph: (301)763-8000 x7274 fantasy
Fax:(301)763-8545 V.S.Naipaul
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
