| Re: Resolving Built-ins and FORWARD_FUNCTION [message #37330 is a reply to message #37329] |
Tue, 09 December 2003 12:57   |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Tue, 09 Dec 2003 12:47:20 -0700, Craig Markwardt wrote:
> JD Smith <jdsmith@as.arizona.edu> writes:
>> Thanks Craig. RSI has filed an internal bug-fix request on this one,
>> and suggested a workaround of using "COMPILE_OPT IDL2" in place of
>> FORWARD_FUNCTION. Of course, this would not really help Wayne, who is
>> using FORWARD_FUNCTION to allow NasaLib to run for older IDL 5.x
>> versions (COMPILE_OPT was introduced in v5.3). And it also doesn't
>> help if you're "compiling" in code from libraries over which you have
>> no control.
>>
>> I'm not sure why nobody complained: the bug is present as far back as
>> v5.5 (which is the earliest version I had to test). The test is easy,
>> if you have AstroLib:
>
> I confirmed the problem is present on IDL's 5.1 through 5.4 as well.
>
>
>
>> Because I knew I could get you to do it for me ;). Next question I
>> should probably find out for myself: is there a programmatic way to
>> tell if you're running from a restored SAV file or from real, live
>> source? Can you tell I've almost never built a routine SAV file? I'm
>> trying to see if I can get a large package to run with the IDLVM.
>
> You could probably look for .sav/.SAV in the source file name?
>
> I really don't use IDL save files for routines any more, after a certain
> large corporation (name similar to Kodiak) threatened a potential
> lawsuit against me.
Yes, I think we all were aghast that you'd be targeted in that way.
Also amazing was the notion that the simple .sav format could be
considered a copyright protection device. But if you want your users
to have access through the IDLVM, there is no other way.
Thanks,
JD
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
