comp.lang.idl-pvwave archive: archive

Home » Public Forums » archive » IDL Memory Leaks

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

Re: IDL Memory Leaks [message #27830 is a reply to message #27679]

Tue, 06 November 2001 13:21

Stein Vidar Hagfors H[1] is currently offline

Stein Vidar Hagfors H[1]
Messages: 56
Registered: February 2000

Member

David Fanning <david@dfanning.com> writes:

> JD Smith (jdsmith@astro.cornell.edu) writes:
>
>> Correction, kindly pointed out by an RSI developer... the feature
>> introduced to put a halt to David's perverse misuse of base widgets was
>> *handles*, not pointers. Interestingly, he also filled me in that
>> handles in fact *were* base widgets internally, stripped of everything
>> by the uvalue. I had obviously attempted to elide those from my memory,
>> and not without due cause. Let's hope we remember handles only as a
>> curious side-excursion in IDL history, and insist on pointers in all our
>> code.
>
> While we are getting a history lesson, I'll just
> point out that using unrealized base widgets as pointers,
> handles, or whatever, was not my idea. Like most of my
> really good ideas, I stole this one from someone smarter
> than me, Josh Goldstein, who was one of the best IDL programmers
> I ever saw. He could write IDL code faster than I could think!
>
> I admit that I publicized this perverse idea,
> but only because I found it useful for building
> weird data sets and I found the notion of "pointers"
> helpful in flogging IDL programming courses.
>
> I still run into an occasional program that uses
> unrealized base widgets in this way. And I'm
> happy to say those programs still run. :-)

Hey! I don't know where *you* got this idea from, but *I* have
programs (still in use) from 1994 (the documentation headers were
added 11 June that year..). In one of them, I even mention that "in
IDL versions 3.1 or later," this or that may appear to disappear, but
can always be recovered through a different routine (since the
introduction of the NO_COPY keyword...).

But alas, I think I converted to handles somewhere along the line..

--
------------------------------------------------------------ --------------
Stein Vidar Hagfors Haugan
ESA SOHO SOC/European Space Agency Science Operations Coordinator for SOHO

NASA Goddard Space Flight Center, Email: shaugan@esa.nascom.nasa.gov
Mail Code 682.3, Bld. 26, Room G-1, Tel.: 1-301-286-9028/240-354-6066
Greenbelt, Maryland 20771, USA. Fax: 1-301-286-0264
------------------------------------------------------------ --------------

Report message to a moderator

[Message index]

		IDL Memory Leaks By: Myron Brown on Mon, 05 November 2001 09:53
		Re: IDL Memory Leaks By: Stein Vidar Hagfors H[1] on Tue, 06 November 2001 13:21
		Re: IDL Memory Leaks By: David Fanning on Tue, 06 November 2001 10:16
		Re: IDL Memory Leaks By: David Fanning on Tue, 06 November 2001 06:57
		Re: IDL Memory Leaks By: R.Bauer on Tue, 06 November 2001 02:33
		Re: IDL Memory Leaks By: alt on Mon, 05 November 2001 22:15
		Re: IDL Memory Leaks By: David Fanning on Mon, 05 November 2001 17:14
		Re: IDL Memory Leaks By: John-David T. Smith on Mon, 05 November 2001 14:53
		Re: IDL Memory Leaks By: David Fanning on Mon, 05 November 2001 14:35

Previous Topic:	Re: IDL 5.5 call_external passing strings
Next Topic:	how to save the xobjview image into a file IN COLOR ?

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Oct 12 02:33:27 PDT 2025

Total time taken to generate the page: 1.43847 seconds