comp.lang.idl-pvwave archive: archive » About call_external, AUTO

Home » Public Forums » archive » About call_external, AUTO_GLUE and gcc

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

Re: About call_external, AUTO_GLUE and gcc [message #39651 is a reply to message #39564]

Tue, 01 June 2004 09:16

profxtjb
Messages: 22
Registered: October 2003

Junior Member

"mwvogel" <mvogel@rdiag.fgg.eur.nl> wrote in message news:<c9fsk2$fai$1@brutus.eur.nl>...

<scratching head>
Well, I guess that conclusively concludes the conclusion that I need
to follow the unconventional practice of reading the instructions!
:)

Thanks!

> Concerning CALL_EXTERNAL, there seems to be an /UNLOAD switch. I guess that
> should do it.
> The excerpt from the help file :
> ***************************
> UNLOAD
>
> Normally, IDL keeps Image loaded in memory after the call to CALL_EXTERNAL
> completes. This is done for efficiency
> -loading a sharable object can be a slow operation. Setting the UNLOAD
> keyword will cause IDL to unload Image after the call to it is complete.
> This is useful if you are debugging code in Image

Report message to a moderator

[Message index]

		About call_external, AUTO_GLUE and gcc By: profxtjb on Fri, 28 May 2004 18:54
		Re: About call_external, AUTO_GLUE and gcc By: profxtjb on Tue, 01 June 2004 09:16
		Re: About call_external, AUTO_GLUE and gcc By: mwvogel on Mon, 31 May 2004 11:13

Previous Topic:	Re: Bug in ISHFT? (NOT)
Next Topic:	CURVEFIT

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 11:02:56 PDT 2025

Total time taken to generate the page: 1.59824 seconds