Yes (it is "ropey"). Good practice would be to find the error and fix it. Of course if the error is in a component you don't have source for (which is also a no-no) then you may not be able to do anything about it and your solution may be required. Even so it is still ropey. ;-)
If the error is due to something your code is doing then of course there is no excuse and for many good reasons it should be fixed instead of hidden. David P.S. As others have mentioned Free is far more normal than Destroy (which bypasses the nil object checking). > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Alistair George > Sent: Monday, 10 March 2003 3:46 PM > To: Multiple recipients of list delphi > Subject: [DUG]: Is this ropey practice? > > > Hi this is what i have been doing in the past to circumvent some > possible errors > when they are no big deal errors: > try dmon.Form1.Destroy; except; end; > > Any comments? > > Thanks, > Al+ > > ------------------------------------------------------------------ > --------- > 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/ --------------------------------------------------------------------------- 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/
