Brian Oxley wrote:
Mario Ivankovits wrote:
... this "MaybeBackup" is a thing we could discuss at its own.
How should a backup be done and named?
a) backup to *.bak
b) use versioning - e.g. *.bak_01, *.bak_02
b.1) with max versions
c) use timestamping - e.g. *.bak_20050101
c.1) but not more than 20 backups
Just an example. What I did was give the WhimFile instance methods to
cover these cases so that extending classes could implement their own
policy. I didn't intend to clutter my example with these issues! I
should be more careful.
No No - my fault, I tend to be a little bit rush if it comes to new
functions and then such "details" comes into my mind "too early".
Is there a format I should follow in writing said proposal?
I think it is sufficient if you just write it into a mail.
Method(args, ...)
Description
Method(args, ...)
Description
... and so on.
Ciao,
Mario
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
