> I sometimes bracket the contents of the onclose/ondestroy with try
> except and junk the exception to avoid the above. I have
> often wondered
> if I should do this as standard. At least the user will see
> a graceful
> degradation of the app.... instead of having to restart it.
IMHO I wouldn't standardise this or even do it if it could be avoided.
Concealing something crashing like this could
Be leaving the application in a badly unresolved state where continued
operation could just get worse and worse. I think
It is worth the time spent examining such things as why destructors are
crashing and stopping it. I can't think of
A coding example where it would be "not a bug" to raise unresolved
exceptions or AV's in a desctructor.
>Is this strictly necesary? reason being that if anything fails during
the forms destructuction, the application wont
> allow another form of the
>same class and also it results in AV on the exit of the app
Neven, I haven't heard of anything like this happening except in cases
where your form may be accessing some kind of shared
Memory or resource that, once crashed keeps crashing. So the only advise
here is also to determine why it's crashing and fix that problem.
Regards
Kyley
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
