| Re: exposing variables to higher program levels [message #54065] |
Thu, 17 May 2007 04:41 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Lasse Clausen writes:
> So I tried:
>
> pro example2
> example
> print, haha
> end
>
> pro example
> void = scope_varfetch('haha', /enter, level=-1)
> void = 'Hello'
> end
>
> But alas!:
> IDL> example2
> IDL: Variable is undefined: <No name>.
> IDL: Execution halted at: EXAMPLE 7 /home/lbnc1/idl/
> example.pro
> IDL: EXAMPLE2 2 /home/lbnc1/idl/
> example.pro
> IDL: $MAIN$
>
>
> What am I doing wrong? Is that not exactly, what Chris wants?
You need to read that article again:
http://www.dfanning.com/tips/access_main_vars.html
Here is code (written with proper naming convention, BTW) that
works:
pro example
(scope_varfetch('haha', /enter, level=-1)) = 'Hello'
end
pro example2
example
print, haha
end
And then,
IDL> example2
Hello
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: exposing variables to higher program levels [message #54067 is a reply to message #54065] |
Thu, 17 May 2007 04:08  |
lasse
Messages: 48
Registered: February 2007
|
Member |
|
|
On 17 May, 02:12, Christopher Thom <c...@oddjob.uchicago.edu> wrote:
> Hi all,
>
> I've been thinking for a while that I really need to kick my addition to
> the IDL 'save' command...which, while very convenient, has the nasty habit
> of not being as portable as I'd like. I recently got bitten by this
> (again!).
>
> So this afternoon I started tooling around with two routines that would
> dump all the variables I want into an anonymous structure, and save them
> to a binary fits table. This works quite nicely, and I can then restore
> the structure from the fits file, and extract the variables from the
> structure.
>
> The one catch, though, is that I would like to wrap this up in two
> routines, to do the bundling and unbundling from the needed
> structure...but this seems to require the ability to export variables to a
> higher program level. I don't think it's simply as easy as returning them
> as parameters, since there are an arbitrary number of variables one might
> restore from a given fits "save" file.
>
> Any ideas on how to do this (or code already written) would be greatly
> appreciated.
>
> cheers
> chris
Hi,
I have been reading in the help of SCOPE_VARFETCH and under the ENTER
keyword it says:
By default, SCOPE_VARFETCH will return only variables that already
exist in the specified scope. Attempts to access a nonexistent
variable will cause IDL to issue an error and halt execution of the
program. Set this keyword to alter this behavior. If ENTER is set and
the desired variable does not exist in the specified scope,
SCOPE_VARFETCH will create a new variable within that scope and return
the new variable. This keyword can be used to export data into other
scopes. Generally, the scope of the calling routine and that of $MAIN$
are most likely to be useful destinations.
So I tried:
pro example2
example
print, haha
end
pro example
void = scope_varfetch('haha', /enter, level=-1)
void = 'Hello'
end
But alas!:
IDL> example2
IDL: Variable is undefined: <No name>.
IDL: Execution halted at: EXAMPLE 7 /home/lbnc1/idl/
example.pro
IDL: EXAMPLE2 2 /home/lbnc1/idl/
example.pro
IDL: $MAIN$
What am I doing wrong? Is that not exactly, what Chris wants?
Cheers
Lasse
|
|
|
|
|
|
| Re: exposing variables to higher program levels [message #54072 is a reply to message #54071] |
Wed, 16 May 2007 21:37 |
Christopher Thom
Messages: 66
Registered: October 2006
|
Member |
|
|
Quoth David Fanning:
> Christopher Thom writes:
>
>> The one catch, though, is that I would like to wrap this up in two
>> routines, to do the bundling and unbundling from the needed
>> structure...but this seems to require the ability to export variables to a
>> higher program level. I don't think it's simply as easy as returning them
>> as parameters, since there are an arbitrary number of variables one might
>> restore from a given fits "save" file.
>>
>> Any ideas on how to do this (or code already written) would be greatly
>> appreciated.
>
> SCOPE_VARFETCH is what you are looking for.
thanks!
chris
|
|
|
|
| Re: exposing variables to higher program levels [message #54076 is a reply to message #54072] |
Wed, 16 May 2007 19:28 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Christopher Thom writes:
> The one catch, though, is that I would like to wrap this up in two
> routines, to do the bundling and unbundling from the needed
> structure...but this seems to require the ability to export variables to a
> higher program level. I don't think it's simply as easy as returning them
> as parameters, since there are an arbitrary number of variables one might
> restore from a given fits "save" file.
>
> Any ideas on how to do this (or code already written) would be greatly
> appreciated.
SCOPE_VARFETCH is what you are looking for.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
