Re: Function referencing/automatic defintion question. [message #35383 is a reply to message #35382] |
Fri, 30 May 2003 07:12   |
Robert.S.Hill.1
Messages: 3 Registered: May 2003
|
Junior Member |
|
|
Paul van Delst <paul.vandelst@noaa.gov> writes:
> Here is the snippet of code where the weird stuff occurs (I commented
> out the COMPILE STRICTARR statement):
>
> ; ---------------------------------------------
> ; Create and allocate the coefficient structure
> ; ---------------------------------------------
> ; -- Create the structure
> EmisCoeff = { EmisCoeff }
>
> print,routine_info(/FUNCTIONS,/SOURCE)
> stop ;***NOTE the STOP ***
> ; -- Allocate it
> Result = Allocate_EmisCoeff( n_Wind_Speeds, n_Coefficients,
> n_Channels, $
> EmisCoeff )
> IF ( Result NE SUCCESS ) THEN $
> MESSAGE, 'Error allocating EmisCoeff structure', $
> /NONAME, /NOPRINT
I interject myself into this discussion with great trepidation, but...
Isn't this a compile-time issue, rather than a run-time issue? Unless
Allocate_EmisCoeff has been compiled already when the routine containing
the snippet is compiled, then Allocate_EmisCoeff is going to look like a
variable no matter what the situation is at run time. Or did I miss
something in the previous discussion, in which case I am baffled, too.
But this is precisely the sort of thing that forward_function takes care
of.
-Bob Hill
|
|
|