Re: Catching I/O errors on RESTORE [message #29802 is a reply to message #29671] |
Tue, 12 March 2002 16:06  |
Craig Markwardt
Messages: 1869 Registered: November 1996
|
Senior Member |
|
|
alt@iszf.irk.ru (Altyntsev Dmitriy) writes:
>>
>> I would very much like to hear reports on how well the CMSVLIB SAVE
>> library does with corrupted files. It should report errors back to
>> user programs without crashing.
>>
> It really does. Thanks. At least as far as I had opportunity to check.
> I had problems with ordinary RESTORE and none of them is present now.
> I am going to get huge statistics on CMSVLIB stability during my
> software package running (save-restore every 10 sec through network)
> this summer (forest fire season). Certainly I will inform you about
> results.
Thanks for the report!
> Craig, it would be impudence to wish more but if your library had an
> ability to replace (expand, squeeze, delete) variables in sav-files it
> would be absolutely indispensable for organizing of IDL file container
> and would be used very widely as I think. Just a wish, sorry :-))
You're right. It would be impudence.
Craig
[ Joking of course. ] Replacing, expanding, squeezing, deleting, are
all much harder operations than what CMSAVE can do right now. The
/APPEND option was "easy" in the sense that all you do is tack on some
more data at the end.
You might be amazed, at least I was, that IDL does not have a way to
trim an existing file. I'm talking about the same thing that
ftruncate() does in C. So "squeezing" would be very hard.
Probably then the easiest way to "replace" a variable is to restore
the file, replace the variable you want, then save it again. At least
at the moment.
--
------------------------------------------------------------ --------------
Craig B. Markwardt, Ph.D. EMAIL: craigmnet@cow.physics.wisc.edu
Astrophysics, IDL, Finance, Derivatives | Remove "net" for better response
------------------------------------------------------------ --------------
|
|
|