comp.lang.idl-pvwave archive: archive » Re: Function as variable issue but in own file

Home » Public Forums » archive » Re: Function as variable issue but in own file

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

Re: Function as variable issue but in own file [message #68593]

Fri, 13 November 2009 15:12

David Fanning
Messages: 11724
Registered: August 2001

Senior Member

rdh writes:

> I'm getting the error "Variable is undefined: foobar" for one of my
> functions when I save and run my program as a standalone .sav file.
> Everything works fine directly in IDL. The function is in it's own
> file called foobar.pro. I thought this was supposed to resolve any
> compile issues....I also run resolve_all before saving the standalone
> file. And, when checking the compile output, foobar.pro is actually
> compiled before all the procedures and functions that call it. What
> else am I missing?

Off-hand, I would say you were missing COMPILE_OPT STRICTARR
in all of your procedures and functions.

Otherwise, I suspect at least one of your assumptions
about the facts as you present them is wrong. :-)

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.")

Report message to a moderator

[Message index]

Re: Function as variable issue but in own file

By: David Fanning on Fri, 13 November 2009 15:12

Previous Topic:	Function as variable issue but in own file
Next Topic:	Programmatic access to IDL filesystem context

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Dec 01 03:16:53 PST 2025

Total time taken to generate the page: 0.71868 seconds