comp.lang.idl-pvwave archive: archive » Resolve_all: bogus unresolved references

Home » Public Forums » archive » Resolve_all: bogus unresolved references

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

Re: Resolve_all: bogus unresolved references [message #37163 is a reply to message #36492]

Mon, 17 November 2003 00:25

Karsten Rodenacker
Messages: 98
Registered: July 1997

Member

In addition to the undefined procedures TRNLOG,DELLOG,SETLOG mentioned
by William Gallery I get messages with quite standard routines:

% Attempt to call undefined procedure/function: 'COMPLEX'.
% Execution halted at: RESOLVE_ALL_BODY 280
D:\RSI\IDL60\lib\resolve_all.pro
% RESOLVE_ALL 332
D:\RSI\IDL60\lib\resolve_all.pro
% $MAIN$
...
% Attempt to call undefined procedure/function: 'DCOMPLEX'.
% Attempt to call undefined procedure/function: 'FIX'.
% Attempt to call undefined procedure/function: 'HANDLE_CREATE'.
% Attempt to call undefined procedure/function: 'MAKE_ARRAY'.
% Attempt to call undefined procedure/function: 'OBJ_CLASS'.
% Attempt to call undefined procedure/function: 'PTRARR'.
% Attempt to call undefined procedure/function: 'PTR_NEW'.
% Attempt to call undefined procedure/function: 'ROUTINE_NAMES'.
% Attempt to call undefined procedure/function: 'UINT'.
...

Maybe there is an idea in the group to mend that behaviour?
Regards
Karsten Rodenacker

William Gallery schrieb:

> I have an idl program I wish to distribute as an idl save set. When I run
> "resolve_all,/cont' on it, It lists three unresoved routines:
> ....
> % Compiled module: POLY_FIT.
> % Attempt to call undefined procedure/function: 'TRNLOG'.
> % Execution halted at: RESOLVE_ALL_BODY 117
> C:\RSI\IDL56\lib\resolve_all.pro
> % RESOLVE_ALL 162
> C:\RSI\IDL56\lib\resolve_all.pro
> % $MAIN$
> % Compiled module: COMBINE_SIGNALS.
> % Attempt to call undefined procedure/function: 'DELLOG'.
> % Execution halted at: RESOLVE_ALL_BODY 117
> C:\RSI\IDL56\lib\resolve_all.pro
> % RESOLVE_ALL 161
> C:\RSI\IDL56\lib\resolve_all.pro
> % $MAIN$
> % Attempt to call undefined procedure/function: 'SETLOG'.
> % Execution halted at: RESOLVE_ALL_BODY 117
> C:\RSI\IDL56\lib\resolve_all.pro
> % RESOLVE_ALL 161
> C:\RSI\IDL56\lib\resolve_all.pro
> % $MAIN$
> % Compiled module: RESISTANT_MEAN.
> ...
>
> However, I have searched everywhere for anything named trnlog, dellog or
> setlog using:
>
> grep -iR trnlog ./
>
> I looked in the current directory and below, the main idl directory and
> below, and all directories included in !Path and below and found nothing.
> The program runs fine as is. I believe these messages are benign but I
> would like to find their cause.
>
> Is there a way to determine where trnlog is called from? Has anyone seen
> similar messages?
>
> IDL 5.6
> Windows NT
>
>
> Cheers
>
> Bill Gallery
> Frontier Technology, Inc.
>
>

Report message to a moderator

[Message index]

		Resolve_all: bogus unresolved references By: William Gallery on Tue, 23 September 2003 07:40
		Re: Resolve_all: bogus unresolved references By: Craig Markwardt on Mon, 17 November 2003 08:58
		Re: Resolve_all: bogus unresolved references By: Karsten Rodenacker on Mon, 17 November 2003 08:25
		Re: Resolve_all: bogus unresolved references By: Craig Markwardt on Mon, 17 November 2003 07:44
		Re: Resolve_all: bogus unresolved references By: David Fanning on Mon, 17 November 2003 06:32
		Re: Resolve_all: bogus unresolved references By: Karsten Rodenacker on Mon, 17 November 2003 06:27
		Re: Resolve_all: bogus unresolved references By: David Fanning on Mon, 17 November 2003 05:26
		Re: Resolve_all: bogus unresolved references By: Karsten Rodenacker on Mon, 17 November 2003 01:01
		Re: Resolve_all: bogus unresolved references By: Karsten Rodenacker on Mon, 17 November 2003 00:25

Previous Topic:	filtering images in the fourier domain
Next Topic:	Advice on making a plot

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Oct 12 17:13:46 PDT 2025

Total time taken to generate the page: 2.23922 seconds