comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: Recursive object destruction, Was: IDL Shapefile Object
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Recursive object destruction, Was: IDL Shapefile Object [message #28275] Sat, 01 December 2001 07:58
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
Richard Younger (younger@ll.mit.edu) writes:

> On the down side, there's some issues with the recursive passing of
> structure members. Since structure members are always passed by value,
> I'm a little worried that using this destroy routine on, say, structures
> with large arrays in them would use up more memory (and time spent
> copying data to be destroyed anyway) than is reasonable. Does anybody
> have suggestions on this? Am I right to be worried?

Don't know. I've been worrying all morning about
whether I was going to have to write an example
data set to test this. I've decided to live with
uncertainty. :-)

> So I don't know if some of the choices I made are the correct ones. Am I
> using _REF_EXTRA right?

Nearly. I would change this line:

'OBJREF': OBJ_DESTROY, thing, _REF_EXTRA=extr

To this:

'OBJREF': OBJ_DESTROY, thing, _EXTRA=extr

The final call in a chain will have to be done with
_Extra.

> Is there any point to checking whether I'm
> dealing with a (structure member) copy or the real McCoy?

If we are talking about pointers and objects in structures,
I don't see that it makes any difference at all if you
are dealing with a copy or the real thing. The copy points
to the real thing. That's what is important, it seems to me.

> What about
> undefining vs. setting the variable to zero and redundant destruction?

Undefining verses setting a variable to zero is more a
matter of style, I think, than anything of substance.
>
> Are there flaws that I haven't seen?

Oh, there are *always* flaws you haven't seen yet.
That's part of the mystery of programming.

Cheers,

David
--
David W. Fanning, Ph.D.
Fanning Software Consulting
Phone: 970-221-0438, E-mail: david@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155
[Message index]
 
Read Message
Previous Topic: Calling IDL from Fortran called by IDL
Next Topic: Humble request

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 13:04:08 PDT 2025

Total time taken to generate the page: 0.00410 seconds