comp.lang.idl-pvwave archive: archive » Re: yet another idl memory question

Home » Public Forums » archive » Re: yet another idl memory question

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

Re: yet another idl memory question [message #66689 is a reply to message #66687]

Thu, 04 June 2009 10:06

David Fanning
Messages: 11724
Registered: August 2001

Senior Member

Jean H. writes:

> in which case you may want to save the
> variable(s) to a file, free the memory (data=0B) and start processing
> the next file.

Of course, data=0B doesn't free *all* the memory,
and doing this many times leads, I suspect, to the memory
fragmentation that is the heart of the problem. I suggest
you use UNDEFINE. That really does release *all* the memory
associated with a variable. And it elegantly indicates
what the code is actually doing, too, a significant
advantage for people reading your code after you have
run off to the tropics with that hot financial analyst
over in the head shed. :-)

http://www.dfanning.com/programs/undefine.pro

Cheers,

David

--
David Fanning, Ph.D.
Coyote's Guide to IDL Programming (www.dfanning.com)
Sepore ma de ni thui. ("Perhaps thou speakest truth.")

Report message to a moderator

[Message index]

		Re: yet another idl memory question By: Karl[1] on Thu, 04 June 2009 13:06
		Re: yet another idl memory question By: David Fanning on Thu, 04 June 2009 10:06
		Re: yet another idl memory question By: Jean H. on Thu, 04 June 2009 09:29
		Re: yet another idl memory question By: pgrigis on Mon, 08 June 2009 11:22

Previous Topic:	Saving Current Graphics Window in TIFF
Next Topic:	Distributing code in IDL 7.1

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Nov 30 02:20:06 PST 2025

Total time taken to generate the page: 1.03884 seconds