| exposing variables to higher program levels [message #54077] |
Wed, 16 May 2007 18:12 |
Christopher Thom
Messages: 66
Registered: October 2006
|
Member |
|
|
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
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
