comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » openr and /get_lun
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
openr and /get_lun [message #19741] Fri, 14 April 2000 00:00 Go to previous message
Craig Markwardt is currently offline  Craig Markwardt
Messages: 1869
Registered: November 1996
Senior Member
I have noticed that the use of /GET_LUN and ERROR keywords to openr is
not as helpful as I would have hoped. Do other have this experience?
The problem is that when an error occurs, it is hard to know whether
the file unit was "gotten" or not.

For example:

pro test1
openr, unit, filename, /get_lun, error=err
free_lun, unit
end

If there was an error, then it is possible that UNIT was never set,
and is hence undefined. FREE_LUN doesn't take undefined variables.

If there is error checking to do, I don't know exactly what it should
be. So I find myself explicitly doing this instead:

pro test2
get_lun, unit
openr, unit, filename, error=err
free_lun, unit
end

Comments?

Craig

--
------------------------------------------------------------ --------------
Craig B. Markwardt, Ph.D. EMAIL: craigmnet@cow.physics.wisc.edu
Astrophysics, IDL, Finance, Derivatives | Remove "net" for better response
------------------------------------------------------------ --------------
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: how to read GRIB format data (NCEP monthly U/VFlux data)
Next Topic: Theater Arts 101: Intro to Lighting Design

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 17:40:29 PDT 2025

Total time taken to generate the page: 0.00399 seconds