comp.lang.idl-pvwave archive: archive » One RETALL is not enough

Home » Public Forums » archive » One RETALL is not enough

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

Re: One RETALL is not enough [message #81996 is a reply to message #81888]

Fri, 02 November 2012 01:13

Yngvar Larsen
Messages: 134
Registered: January 2010

Senior Member

On Friday, 2 November 2012 05:33:42 UTC+1, David Fanning wrote:
> Jim P writes:
>
>> The original posting appears to indicate that the contents of a HASH at the time the
>> destructor was executed included some "bad" pointer references internally. Whether these
>> are references to pointers that are used only internally by the hash or if they are references
>> to "user mode" pointers that have been stored in the hash by user code is unclear.
>> A repeatable case that can be sent to Exelis VIS (support@exelisvis.com) would be helpful
>> if the issue can be tracked to a pathology in the internal IDL class cleanup code.

In IDL version >= 8.0, there should not really be any need for an explicit cleanup method anymore. (Unless you have used external OS resources: open sockets, open files, temp files that needs to be removed, etc.) That is sort of the point with an automatic garbage collector.

--
Yngvar

Report message to a moderator

[Message index]

		One RETALL is not enough By: wlandsman on Fri, 26 October 2012 13:26
		Re: One RETALL is not enough By: Yngvar Larsen on Fri, 02 November 2012 01:13
		Re: One RETALL is not enough By: David Fanning on Thu, 01 November 2012 21:33
		Re: One RETALL is not enough By: Jim Pendleton on Thu, 01 November 2012 20:41

Previous Topic:	Re: cgColor and Widget_Draw Frame problem
Next Topic:	Reading Analog input from IDL

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 11:14:37 PDT 2025

Total time taken to generate the page: 0.80184 seconds