RE: Idl 3.6.1a And Solaris 2.4 [message #4074] |
Tue, 25 April 1995 00:00 |
rivers
Messages: 228 Registered: March 1991
|
Senior Member |
|
|
In article <3nj8r1$2et@hammer.msfc.nasa.gov>, mallozzi@ssl.msfc.nasa.gov writes:
>> Has anyone ever verified whether IDL 3.6.1a and Solaris 2.4 works
>> fine together ?
>
> I tried to call some FORTRAN code (IDL3.6.1a, Solaris 3.3) and ran into
> an error. The FORTRAN required user-input deep down in the set of
> subroutines, and the code does not wait for the input, but continues on
> as if you had entered a null string. I talked to IDL "support", and they
> said that nothing could be done, as IDL sets the tty settings, and there
> is no way to reset them, call the FORTRAN, then set them back.
> IDL "support" solution: Rewrite the code into IDL (even after I told them
> the FORTRAN is more than 10k lines!). Oh well, so much for IDL's
> portability...
I have not tried it yet, but I find it hard to believe you could not reset the
tty settings in a little C or FORTRAN wrapper and then call your routine, and
then set them back when you are done.
I suggest you create a little test routine to isolate the problem and then try
solutions.
____________________________________________________________
Mark Rivers (312) 702-2279 (office)
CARS (312) 702-9951 (secretary)
Univ. of Chicago (312) 702-5454 (FAX)
5640 S. Ellis Ave. (708) 922-0499 (home)
Chicago, IL 60637 rivers@cars3.uchicago.edu (Internet)
|
|
|
RE: Idl 3.6.1a And Solaris 2.4 [message #4078 is a reply to message #4074] |
Tue, 25 April 1995 00:00  |
mallozzi
Messages: 60 Registered: August 1994
|
Member |
|
|
> Has anyone ever verified whether IDL 3.6.1a and Solaris 2.4 works
> fine together ?
I tried to call some FORTRAN code (IDL3.6.1a, Solaris 3.3) and ran into
an error. The FORTRAN required user-input deep down in the set of
subroutines, and the code does not wait for the input, but continues on
as if you had entered a null string. I talked to IDL "support", and they
said that nothing could be done, as IDL sets the tty settings, and there
is no way to reset them, call the FORTRAN, then set them back.
IDL "support" solution: Rewrite the code into IDL (even after I told them
the FORTRAN is more than 10k lines!). Oh well, so much for IDL's
portability...
|
|
|