Home »
Public Forums »
archive »
One file for each procedure/function?
| One file for each procedure/function? [message #30340] |
Fri, 19 April 2002 05:24 |
Pepijn Kenter
Messages: 31
Registered: April 2002
|
Member |
|
|
Hi all.
I'm currently writing analyses software (small programs plus routines) for
an ozon measurement device and I'm new to IDL. A lot of the routines and
programs have already been written and are ready for me to use. These
routines have been grouped together in a few .pro files. These files are
then compiled explicitly (by .compile statements) in the main programs. The
programs are called from the command line.
I'm under the strong impression that this is not the normal way of working
and that you should create one file for each function or procedure, which is
than compiled automaticly when it's needed. These files should be put in a
directory that is included in the !path system variable.
Still, I would like to keep functions that belong to each other grouped
together; if not in one file, then at least in one directory. So I've
devided the routines over a few directories and used the expand_path
function to include these directories in the !path variable.
Is this the best way of working?
Or are there better way's of ordering your routines (like units in pascal)?
I want to keep using the command line to start my programs (i.e. i don't
want to be dependend on .prj files)
I'm not happy with the 'one file for each function' concept but if this is
the way IDL is designed I think I'd better stick to it, rather than using
obscure tricks to circumvent it.
Thanks for your help,
Pepijn Kenter.
|
|
|
|
Current Time: Fri Oct 10 12:41:38 PDT 2025
Total time taken to generate the page: 0.32300 seconds
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
