| Re: Minor bug in 4.0.1 for Win95 [message #6904] |
Wed, 04 September 1996 00:00 |
M.Reuss
Messages: 4
Registered: January 1996
|
Junior Member |
|
|
The Users'Guide for IDL 3.0 says that under Unix,
file units 0,-1, and -2 are tied to stdin, stdout, and stderr,
respectively.
Under VMS, these units are tied to the equivalents
SYS$INPUT,SYS$OUTPUT, and SYS$ERROR.
The Release Notes for IDL (version 3.*) for Windows say that these
three numbers are tied to stdin, stdout, and stderr, too.
I don't know whether there have been major changes to this in IDL 4.*.
Isn't there a good documentation any more?
Matthias Reuss
|
|
|
|
| Re: Minor bug in 4.0.1 for Win95 [message #6915 is a reply to message #6904] |
Tue, 03 September 1996 00:00  |
robert
Messages: 3
Registered: February 1996
|
Junior Member |
|
|
Brian C. Ballard (bballard@orionint.com) wrote:
: Tim Patterson wrote:
: > Eric J. Korpela wrote:
: > > Anyone know what happens on VMS?
: > OPEN VMS:
: > IDL> printf,0
: > IDL> printf,1
: > % PRINTF: File unit is not open: 1.
: > % Execution halted at: $MAIN$
: > IDL> printf,-1
: > IDL> printf,-2
: > IDL> printf,-3
: > % PRINTF: File unit is not within allowed range: -3.
: > % Execution halted at: $MAIN$
: > IDL>
: > Seems to be the same as the Unix side. No crashes anyway.
: > Looks like that's just a MS Windows/IDL problem so far.
: > Tim
: Yep, same thing on Sun Solaris 2.5:
: IDL> printf,0
: IDL> printf,1
: % PRINTF: File unit is not open: 1.
: % Execution halted at: $MAIN$
: IDL> printf,-1
: IDL> printf,-2
: IDL> printf,-3
: % PRINTF: File unit is not within allowed range: -3.
: % Execution halted at: $MAIN$
Same on IRIX5.3. As a point of note, we have -2 for stderr, -1 for stdout,
and finally, just for information,
IDL> print,!journal
0
(system variable !journal: "A read-only long-integer variable containing
the logical unit number of the file used for journal output" Online help)
So what is !journal set to undef W95?
--
Robert Bunting E-mail: robert@aurora.york.ac.uk
Space Geophysics Group Tel:(+44)1904-432277
Dept of Physics, University of York, Fax:(+44)1904-432214
York YO1 5DD U.K. WWW: http://aurora.york.ac.uk/
|
|
|
|
| Re: Minor bug in 4.0.1 for Win95 [message #6920 is a reply to message #6915] |
Mon, 02 September 1996 00:00 |
Brian C. Ballard
Messages: 3
Registered: August 1996
|
Junior Member |
|
|
Tim Patterson wrote:
>
> Eric J. Korpela wrote:
>
>>
>> Anyone know what happens on VMS?
>>
>
> OPEN VMS:
>
> IDL> printf,0
> IDL> printf,1
> % PRINTF: File unit is not open: 1.
> % Execution halted at: $MAIN$
> IDL> printf,-1
>
> IDL> printf,-2
>
> IDL> printf,-3
> % PRINTF: File unit is not within allowed range: -3.
> % Execution halted at: $MAIN$
> IDL>
>
> Seems to be the same as the Unix side. No crashes anyway.
> Looks like that's just a MS Windows/IDL problem so far.
>
> Tim
Yep, same thing on Sun Solaris 2.5:
IDL> printf,0
IDL> printf,1
% PRINTF: File unit is not open: 1.
% Execution halted at: $MAIN$
IDL> printf,-1
IDL> printf,-2
IDL> printf,-3
% PRINTF: File unit is not within allowed range: -3.
% Execution halted at: $MAIN$
--
Brian C. Ballard
Electrical Engineer
E-mail: bballard@orionint.com
WWW : http://www.orionint.com/~bballard/
|
|
|
|
| Re: Minor bug in 4.0.1 for Win95 [message #6923 is a reply to message #6920] |
Fri, 30 August 1996 00:00 |
Tim Patterson
Messages: 65
Registered: October 1995
|
Member |
|
|
Eric J. Korpela wrote:
>
> Anyone know what happens on VMS?
>
OPEN VMS:
IDL> printf,0
IDL> printf,1
% PRINTF: File unit is not open: 1.
% Execution halted at: $MAIN$
IDL> printf,-1
IDL> printf,-2
IDL> printf,-3
% PRINTF: File unit is not within allowed range: -3.
% Execution halted at: $MAIN$
IDL>
Seems to be the same as the Unix side. No crashes anyway.
Looks like that's just a MS Windows/IDL problem so far.
Tim
|
|
|
|
|
|
| Re: Minor bug in 4.0.1 for Win95 [message #6929 is a reply to message #6923] |
Fri, 30 August 1996 00:00 |
Tim Patterson
Messages: 65
Registered: October 1995
|
Member |
|
|
David P. Steele wrote:
>
> In article <brian.jackel.77.001B3BC3@uwo.ca>, brian.jackel@uwo.caJ says...
>>
>> Purely by accident, I found out a one line way to
>> crash IDL Version 4.0.1 (Win32 x86) running under
>> Windows 95. Just type
>>
>> PRINTF,0
>>
>> and it goes boom. Yes, I know it's not a valid use
>> of PRINTF, but the equally stupid PRINTF,1
>> just returns a nice error message.
>>
>> Can anyone reproduce this on other platforms?
>>
>> Brian Jackel
>
> Sure enough, it gives an "Unhandled Exception" error message under Windows for
> Workgroups 3.11.
>
On a digital unix alpha with idl 4.0.1b:
IDL> printf,1
% PRINTF: File unit is not open: 1.
% Execution halted at: $MAIN$
IDL> printf,0
IDL>
So no crash, but no error message either.
Also,
IDL> printf,-1
IDL> printf,-2
IDL> printf,-3
% PRINTF: File unit is not within allowed range: -3.
% Execution halted at: $MAIN$
IDL>
Wonder what file units -1 and -2 are?
Tim
|
|
|
|
| Re: Minor bug in 4.0.1 for Win95 [message #6931 is a reply to message #6923] |
Fri, 30 August 1996 00:00 |
David.Steele
Messages: 8
Registered: April 1996
|
Junior Member |
|
|
In article <brian.jackel.77.001B3BC3@uwo.ca>, brian.jackel@uwo.caJ says...
>
> Purely by accident, I found out a one line way to
> crash IDL Version 4.0.1 (Win32 x86) running under
> Windows 95. Just type
>
> PRINTF,0
>
> and it goes boom. Yes, I know it's not a valid use
> of PRINTF, but the equally stupid PRINTF,1
> just returns a nice error message.
>
> Can anyone reproduce this on other platforms?
>
> Brian Jackel
Sure enough, it gives an "Unhandled Exception" error message under Windows for
Workgroups 3.11.
Dave
--
------------------------------------------------------------ ------------
David P. Steele Ph: (306) 966-6447
ISAS, University of Saskatchewan Fax: (306) 966-6400
116 Science Place David.Steele@usask.ca
Saskatoon SK S7N 5E2 CANSAS::STEELE
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
