| Re: library help -- multiple procedures in one file [message #30958 is a reply to message #30957] |
Fri, 24 May 2002 09:16  |
Liam E. Gumley
Messages: 378 Registered: January 2000
|
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?
>
> Cheers,
> Chris
My preferences:
- One function or procedure per source file,
- All lower case file names,
- UNIX formatting (CR/LF) for newlines,
- Compressed tar files for UNIX users,
- ZIP files for Win/Mac users,
- Available via HTTP.
The only exception to the one function or procedure per file rule would
be if you have several tightly coupled routines that naturally belong
together, such as the definition of an object and it's methods.
Cheers,
Liam.
Practical IDL Programming
http://www.gumley.com/
|
|
|
|