| Re: POLY_FIT backward-compatible solution: Use 4.0. [message #11520] |
Mon, 30 March 1998 00:00 |
davidf
Messages: 2866
Registered: September 1996
|
Senior Member |
|
|
Russ Welti (on mapper) (rwelti@mapper.mbt.washington.edu) writes:
> For anyone who, like me, supports IDL installations still
> using 4.0, there is no way to have a single source version
> of your IDL application which uses the new 5.0 POLY_FIT,
> since the 4.0 version has no /DOUBLE keyword.
>
> Until the whole world uses IDL 5.0, the solution must be to
> use the 4.0 POLY_FIT and distribute it with your source code,
> so the 5.0 site will have it. There is no accuracy penalty, and
> I can't perceive any speed differences.
>
> That is the only way to avoid having version-
> dependent code. (I don't find anything in the Index under
> "version" that would let me determine the IDL engine's
> version, anyway, even if I were interested in doing that
> kind of workaround...)
I agree that version-dependent code is a pain, but sometimes
it is inevitable. !VERSION will tell you what you are running.
Cheers,
David
-----------------------------------------------------------
David Fanning, Ph.D.
Fanning Software Consulting
E-Mail: davidf@dfanning.com
Phone: 970-221-0438
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
