| Re: Resolve_all: bogus unresolved references [message #37162 is a reply to message #36492] |
Mon, 17 November 2003 01:01   |
Karsten Rodenacker
Messages: 98
Registered: July 1997
|
Member |
|
|
In the meanwhile I found the source of these messages. All mentioned
routines are 'defined' by forward_function in the cmsavelib software of
Craig Markwardt. After commenting out these lines (without testing
further functionality) the messages disappear.
However after compiling an object I am messing now around with other
missing routines I never heard about. Perhaps there is another
historical OS still hidden?
Regards
Karsten
% Attempt to call undefined procedure/function: 'FW_QUERYDEFAULTSTYLE'.
% 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: 'FW_QUERYNAMEDSTYLE'.
% Attempt to call undefined procedure/function: 'FW_UPDATEDATAWINDOW'.
% Attempt to call undefined procedure/function: 'FW_CWDIMSIZES'.
% Attempt to call undefined procedure/function: 'FW_DATABROWSER'.
% Attempt to call undefined procedure/function: 'FW_GETDATAFROMTEXTWIDGET'.
% Attempt to call undefined procedure/function: 'FW_QUERYOKTODELETEDATA'.
% Attempt to call undefined procedure/function: 'FW_QUERYSTYLELIST'.
Karsten Rodenacker schrieb:
> 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.
>>
>>
>
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
