Re: More problems with Build Project, IDLDE vs IDLRT question [message #69071] |
Wed, 23 December 2009 08:40  |
j.coenia@gmail.com
Messages: 36 Registered: December 2008
|
Member |
|
|
> print, routine_filepath('myfunction',/is_func)
Thanks, it prints nothing, which means the routine is not in the list
of currently compiled routines, so now I am even more confused. How
can it come up with a keyword-not-allowed error from IDLRT for a
routine that is (apparently) not even compiled? Shouldn't it just
have an undefined-routine error in that case? (I also tried with the /
either switch and got the same non-result.)
There's really no way to just run a program in IDLDE to sort of
simulate IDLRT, without the development environment window actually
popping up? I just don't think I'm going to be able to build a
working, stable binary like this.
(It only works if I go through every GUI step while running the app in
IDLDE, then build, but that's impossible, since I can't anticipate and
perform every single user action before each build...)
|
|
|
|
Re: More problems with Build Project, IDLDE vs IDLRT question [message #69268 is a reply to message #69071] |
Wed, 23 December 2009 09:34  |
David Fanning
Messages: 11724 Registered: August 2001
|
Senior Member |
|
|
j.coenia@gmail.com writes:
> Thanks, it prints nothing, which means the routine is not in the list
> of currently compiled routines, so now I am even more confused. How
> can it come up with a keyword-not-allowed error from IDLRT for a
> routine that is (apparently) not even compiled? Shouldn't it just
> have an undefined-routine error in that case? (I also tried with the /
> either switch and got the same non-result.)
This sort of begs the question of whether this call can
find anything from the IDL command line in a new IDL
session:
IDL> Resolve_Routine, 'myfunction', /EITHER
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.")
|
|
|