comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » functions considered as variables
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: functions considered as variables [message #11118 is a reply to message #11056] Wed, 11 March 1998 00:00 Go to previous messageGo to previous message
dirk is currently offline  dirk
Messages: 15
Registered: March 1998
Junior Member
In article <3500B36D.A8@mail.arc.nasa.gov>,
Selwyn Yee <syee@mail.arc.nasa.gov> wrote:
> I've seen this before. It happens when, in your .pro file, you are
> trying to call a function which has not yet been compiled. Either the
> function is in a
> different module, or is in the same .pro file, but below your calling
> statement.
> Because IDL is an interpretive language, it executes and/or compiles the
> code in your .pro file from top to bottom. Your function call:
[snip]
>
> The solution is to use the forward_function command in IDL. The syntax
> is:
>
> forward_function function1, function2, ...
>

Had this problem just the other day.

The other (and coding free) solution is to just compile your driver
function twice. On the first pass, it will misinterpret the information
in the driver, but on the second pass, the support functions will be
interpretted properly as functions (instead of arrays).

I'm not sure if this will work if you have very intricate among your
support functions.

but IDL> .run foo.pro
IDL> .run foo.pro

will work for the simple things.

- Dirk
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Memory Mapped files For IDL (UNIX)
Next Topic: Re: IDL 5.0 widget bug?

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Dec 05 06:50:20 PST 2025

Total time taken to generate the page: 0.01411 seconds