comp.lang.idl-pvwave archive: archive » Releasing memory in IDL

Home » Public Forums » archive » Releasing memory in IDL

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Releasing memory in IDL [message #58317 is a reply to message #58250]

Wed, 23 January 2008 14:11

Jean H.
Messages: 472
Registered: July 2006

Senior Member

Jaime wrote:
> I dug into the code and found that these variables are defined in a
> COMMON block. Why are they still using memory after the program
> finished? can they be destroyed altogether (e.g. common_block=0)?
>
> Best,
> Jaime
the help file says:
[...]
Variables in a common statement have a global scope within procedures
defining the same common block. Unlike local variables, variables in
common blocks are not destroyed when a procedure is exited.

I guess you could write a procedure to erase these values... but as
David pointed out, there is probably a reason why these values are saved
in a common block!... you might be using them in a different function!
If you are sure you a) don't need data from another function and b) this
data will not be used in another function, then I guess you could simply
remove the common block... so your data will "die" at the end of the
function

Jean

Report message to a moderator

[Message index]

		Releasing memory in IDL By: Jaime on Wed, 23 January 2008 06:44
		Re: Releasing memory in IDL By: Jaime on Wed, 23 January 2008 21:07
		Re: Releasing memory in IDL By: David Fanning on Wed, 23 January 2008 14:40
		Re: Releasing memory in IDL By: Jean H. on Wed, 23 January 2008 14:11
		Re: Releasing memory in IDL By: Jaime on Wed, 23 January 2008 14:05
		Re: Releasing memory in IDL By: David Fanning on Wed, 23 January 2008 13:48

Previous Topic:	Re: code for Kendall trend test
Next Topic:	code for Kendall trend test

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Oct 12 13:49:58 PDT 2025

Total time taken to generate the page: 0.08071 seconds