| Re: RESOLVE_ALL problem [message #61958] |
Tue, 12 August 2008 09:35 |
b_gom
Messages: 105
Registered: April 2003
|
Senior Member |
|
|
On Aug 12, 2:22 am, Allan Whiteford
<allan.rem...@phys.remove.strath.ac.remove.uk> wrote:
> If you've got a line of code somewhere which has a call_function call
> but you're calling it like a *procedure* then you'll get this error.
That was it- Thanks! I had to search through a lot of utility
procedures to find the culprit.
|
|
|
|
| Re: RESOLVE_ALL problem [message #61960 is a reply to message #61958] |
Tue, 12 August 2008 01:22  |
Allan Whiteford
Messages: 117
Registered: June 2006
|
Senior Member |
|
|
b_gom@hotmail.com wrote:
> I'm trying to build a .sav file from a project that used to work, but
> is now giving the following error when I call RESOLVE_ALL or use the
> 'Build Project' menu option:
>
> % Attempt to call undefined procedure/function: 'CALL_FUNCTION'.
> % Error occurred at: RESOLVE_ALL_BODY 290 C:\Program Files\ITT
> \IDL70\lib\resolve_all.pro
> % RESOLVE_ALL 351 C:\Program Files\ITT
> \IDL70\lib\resolve_all.pro
> % $MAIN$
> % Execution halted at: $MAIN$
>
> Any idea what is causing this? CALL_FUNCTION works properly, so I
> don't know why RESOLVE_ALL chokes on it.
>
> Thanks
If you've got a line of code somewhere which has a call_function call
but you're calling it like a *procedure* then you'll get this error.
For example:
pro test
if 1 eq 0 then begin
call_function,'myfunction'
endif else begin
print,'hello'
endelse
end
will compile and run with no problems because IDL never has to try to
call a *procedure* called call_function. However, resolve_all will choke
on it.
It could, of course, be something else but it's worth checking your code
to make sure all of your call_function calls are calling it like a function.
Thanks,
Allan
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
