| Re: class definition problem [message #13822 is a reply to message #13699] |
Tue, 08 December 1998 00:00   |
davidf
Messages: 2866
Registered: September 1996
|
Senior Member |
|
|
J.D. Smith (jdsmith@astrosun.tn.cornell.edu) writes:
> With a possible addition of
>
> tmp={header, field1:0,field2:0,...}
>
> before the actual class definition. The point is that the class
> definition is a perfect place to define other class specific data
> structures (even if they aren't contained in the class!). I often use
> the __define procedure to set up special event structures used by the
> program.
I'm not so sure the class definition is the "perfect" place to
define data structures used by the program, although I admit
to sometimes using the technique. In fact, I would
say this strategy has to be used with a bit of caution.
I foresee a problem in having a number of *different* named
structures defined with the name HEADER. This could lead to
messy problems depending upon which programs have been run
first in the IDL session.
Safer, I think, to put *all* named structures in their
own structure definition file. Then, of course, you have
the problem of multiple files with the same name and which
will be found first in the Path, etc. Perhaps the problem is
six of one and a half dozen of the other, unless you have
a specific directory on the path specifically for structure
definition files. (No one I know would be so organized!)
The secret, I guess, is knowing what you are doing in the
first place. :-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting
Phone: 970-221-0438 E-Mail: davidf@dfanning.com
Coyote's Guide to IDL Progamming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
