Frank Heckenbach wrote:
First of all, fjf659o.pas is a strange test program anyway. I was wondering about it, and it was on my list of things to have a closer look at again. So if it fails now, I don't consider it serious anyway.
It's supposed to test that `Finalize' does something for files. But what exactly it does, might better be left undefined. So, when the test program checks for a I/O error that can be caught, this might simply be too optimistic. (And file handling has changed internally since it was written, so it's possible that originally, it either caused a bad access that wasn't noticed, as now, or it didn't and does now.)
I think that it is not nice to crash. IMHO we should very clearly state in the documentation that access to a variable after calling `Finalize' on it is illegal, or make it more robust.
BTW do Delphi allow `Finalize' on files?