| Re: library help -- multiple procedures in one file [message #30936] |
Fri, 24 May 2002 13:41  |
R.Bauer
Messages: 1424
Registered: November 1998
|
Senior Member |
|
|
"Liam E. Gumley" wrote:
>
> Craig Markwardt wrote:
> [stuff deleted]
>> By the way I agree with David's suggestions. I am not sure David's
>> are totally compatibile with Liam's recommendations, for example I
>> would say that internal "utility" routines always belong in the main
>> command file, whereas Liam suggests each file has one procedure or
>> function.
>
> That's why I included a caveat in my list of suggestions. For an
> example, my IMDISP image display procedure
>
> http://www.gumley.com/PIP/Free_Software.html
>
> contains several routines that are designed to be called *only* by the
> IMDISP main procedure, and are therefore stored in the IMDISP source
> file. The same would hold true for methods associated with an object.
>
> Cheers,
> Liam.
> Practical IDL Programming
> http://www.gumley.com/
Hi Liam,
We should not forget to use a name conventions if we put
more than one routine in a file.
If we don't there are a lot of conflicts possible.
The routine itselfs is imdisp and all "included" routines
start by imdisp
imdisp is a good example to show this
IMDISP_GETPOS, IMDISP_IMSCALE, IMDISP_IMREGRID, IMDISP_IMSIZE
David mentioned following situation and I aggree to this.
If now for example IMDISP_IMSIZE is so popular to be used alone
or it is useful for an other package it has to be extracted
from this file and then it is a new routine may be "imsize"
in it's own file.
regards
Reimar
--
Reimar Bauer
Institut fuer Stratosphaerische Chemie (ICG-I)
Forschungszentrum Juelich
email: R.Bauer@fz-juelich.de
------------------------------------------------------------ -------
a IDL library at ForschungsZentrum Juelich
http://www.fz-juelich.de/icg/icg1/idl_icglib/idl_lib_intro.h tml
============================================================ =======
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
