comp.lang.idl-pvwave archive: archive » Why Output Keywords Fail in cgWindow

Home » Public Forums » archive » Why Output Keywords Fail in cgWindow

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

Re: Why Output Keywords Fail in cgWindow [message #85468 is a reply to message #85432]

Mon, 12 August 2013 02:34

Fabzi
Messages: 305
Registered: July 2010

Senior Member

Hi,

On 08/03/2013 12:30 PM, bobnnamtrop@gmail.com wrote:
> On Thursday, August 1, 2013 9:30:50 AM UTC-6, David Fanning wrote:
>>> Unfortunately,
>>> CALL_PROCEDURE does not have a mechanism for returning output keywords.
> This is not true. For example,
>
> IDL> call_procedure, 'help', /MEMORY, OUTPUT=mem_out
> IDL> print, mem_out
> heap memory used: 1191740, max: 1192007, gets: 1125, frees: 281

I think it is more related to the use of _EXTRA keywords, isn't it?

IDL> help, _EXTRA={MEMORY:1, OUTPUT:mem_out}
% HELP: Expression must be named variable in this context: <STRING
Array[1]>.
% Execution halted at: $MAIN$

Report message to a moderator

[Message index]

		Why Output Keywords Fail in cgWindow By: David Fanning on Thu, 01 August 2013 08:30
		Re: Why Output Keywords Fail in cgWindow By: Bob[4] on Sat, 03 August 2013 03:30
		Re: Why Output Keywords Fail in cgWindow By: Fabzi on Mon, 12 August 2013 02:34
		Re: Why Output Keywords Fail in cgWindow By: David Fanning on Mon, 12 August 2013 05:25
		Re: Why Output Keywords Fail in cgWindow By: Fabzi on Mon, 12 August 2013 05:41

Previous Topic:	Persistent environment variables (in DLM example)
Next Topic:	IDL_IDLBridge: No gain?

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Dec 02 14:33:40 PST 2025

Total time taken to generate the page: 0.64315 seconds