| Re: Resolve_all: bogus unresolved references [message #36486] |
Tue, 23 September 2003 19:17 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Andrew Cool writes:
> PS : Say David, I hear you've signed up for wheelchair tennis next season?
Actually, I've been injured more or less since December of last
year, so a wheelchair may be in my future. It's been a wrist,
then an elbow, and I am just entering my first tournament
of the year this week. I was expecting my shoulder to
blow out, but maybe it will be a knee. :-)
Cheers,
David
P.S. Let's just say I hope I am a better wheelchair
player than a left-handed player. Even my wife beat
me this summer. :-(
--
David W. Fanning, Ph.D.
Fanning Software Consulting, Inc.
Phone: 970-221-0438, E-mail: david@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155
|
|
|
|
| Re: Resolve_all: bogus unresolved references [message #36488 is a reply to message #36486] |
Tue, 23 September 2003 17:30  |
andrew.cool
Messages: 47
Registered: July 2003
|
Member |
|
|
David Fanning <david@dfanning.com> wrote in message news:<MPG.19da0bfc197eb7d09896f6@news.frii.com>...
> William Gallery writes:
>
>> 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?
>
> Wow. I haven't seen those in a while. :-)
>
> I think those routines are old VMS routines, and I'm
> pretty sure no one is using VMS these days. (Actually,
> I'm just hoping to hear from Andrew Cool, who always
> rises to this bait.)
>
> What I have done is add some dummy files in the IDL lib
> sub-directory. I can't remember now if these are procedures
> or functions, but something like this should work:
>
>
> PRO TRNLOG
> END
>
> That will get you through the RESOLVE_ALL routine in good
> shape, and won't do any damage to your programs.
>
> Cheers,
>
> David
David is of course right, in more ways than one...
And the solution of dummy files on non-VMS platforms for
these three *current* VMS routines is tried & trusted/crusted one.
Note though that TRNLOG is a function, whilst SETLOG and DELLOG
are procedures, when you define your dummies.
Andrew
PS : Say David, I hear you've signed up for wheelchair tennis next season?
|
|
|
|
| Re: Resolve_all: bogus unresolved references [message #36491 is a reply to message #36488] |
Tue, 23 September 2003 07:51 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
William Gallery writes:
> 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?
Wow. I haven't seen those in a while. :-)
I think those routines are old VMS routines, and I'm
pretty sure no one is using VMS these days. (Actually,
I'm just hoping to hear from Andrew Cool, who always
rises to this bait.)
What I have done is add some dummy files in the IDL lib
sub-directory. I can't remember now if these are procedures
or functions, but something like this should work:
PRO TRNLOG
END
That will get you through the RESOLVE_ALL routine in good
shape, and won't do any damage to your programs.
Cheers,
David
--
David W. Fanning, Ph.D.
Fanning Software Consulting, Inc.
Phone: 970-221-0438, E-mail: david@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
