Josef Templ wrote: ad Stores.Reader/Writer:
There are multiple possibilities and it is the question where to stop with the duplication of functionality.
Here is a choice of alternatives:
- a subset of Stores64 covering only simple Reader and Writer procedures (seems to be simple)
- a complete Stores64 (don't know if it is complicated)
- more methods put into Files64.Reader/Writer
- move it all into an extension package (CPC, AppStore) instead of the standard distribution.
I suspect that Doug in not
interpreting the contents of his multi-GByte files, that Files64 is overkill for his needs, and that something like just using WinApi.CopyFile or WinApi.MoveFile is all he needs?
On the other hand, if we do go to the trouble to provide Files64 it is of very limited general use unless we also provide a compatible "Stores64".Reader & Writer.
I think your first two options are the only good ones.
Why do we need a
complete new Stores64; surely the only parts that we want are a new Reader & Writer?
A
complete new Reader & Writer might be the
best solution, but a partial Reader and Writer, as I illustrated earlier, may be a good compromise between utility and implementation effort. We can always add support for Multi-GByte Stores later when a real need for this functionality arises?