Giuliano Colla wrote:
On 02/12/2013 10:02 AM, Mark Morgan Lloyd wrote:
I admit that I was slightly trolling there, since Giuliano was
complaining about exceptions that he wasn't seeing (because, it turns
out, he wasn't catching them).
You catch an exception if you can handle it. If a user for some reasons
has write-protected a configuration file, there's nothing the
application can do about it. One can usually rely on the system default
exception handler to show the error message. If it doesn't happen, then
there's something wrong somewhere.
Yes, but the point that I'm trying to get across is that the earlier you
make sure that you've got full access to the files (i.e. all directories
in the path exist, the file either exists and is writable or you create
it from a template) the easier you make life for yourself. If having the
file is absolutely essential then check for it before you even open the
main form and bomb if it's obvious that there's a problem.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
