On Thu, Mar 05, 2009, Joe Krahn wrote:
> Another question about file I/O. I have my own routines similar to
> amopen() that automatically allocates LUNs. It also makes backup files
> similar to CNS, which is sort of a VMS emulation. A replaced file
> becomes <filename>_1. If <filename>_1 exists, it is moved to
> <filename>_2, and so on up to some max-backup limit.
>
> In general, it is easier to run with file overwriting enabled. This
> feature gives you the ease of use, but saves you from the occasional
> loss of a file that you didn't want to delete.
Again, if we do this, we have to explain it. There are OS-level
routines that will accomplish this for Linux systems, I believe. I
understand the desire for this, but also want to avoid making Amber even
more complex....
...dac
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Sun Mar 08 2009 - 01:08:47 PST
