Right. Thanks for the info. Mark On 11 Dec 2003 at 10:55, Myles Penlington wrote:
> Correct. > For these errors to be trapped, you must have these options turned on. > They cause extra code to be inserted after every operation that can > cause this type of error, and then if an error happens an exception > will be raised. > > One of reasons they are turned off for production code is that they > slow the application down and increase the compiled size of the > application. > > Myles. > > -----Original Message----- > From: Mark Howard [mailto:[EMAIL PROTECTED] > Sent: Thursday, 11 December 2003 10:55 > To: NZ Borland Developers Group - Delphi List > Subject: RE: [DUG] Another debugging question > > > Thanks Myles > OK, well THAT's easy. > So. is there ever any point in having these Run Time error checks > switched on? (Or does Stop on Delphi Exceptions in the debugger > options not trap these errors?) > > Mark > > On 11 Dec 2003 at 10:37, Myles Penlington wrote: > > > The normal practice any production build, is to have "off" to range > > checking, I/O and Overflow. > > > > These are in essence debug type options. > > > > Range check will always at some stage cause issues with mouse > > operations. > > > > Part of the issue is that Delphi's range checking is flawed (or well > > was last time I looked - it reported range check errors on loading > > of negative integers in some cases). > > > > Overflow could be left on, but I can't say I have checked the > > generated code to ensure it will not suffer the same issues as range > > checking. Another way to say this is that I have yet to suffer from > > a Overflow check failure in using Delphi for 6/7 years. > > > > Myles. > > > > > > -----Original Message----- > > From: Mark Howard [mailto:[EMAIL PROTECTED] > > Sent: Thursday, 11 December 2003 10:32 > > To: [EMAIL PROTECTED] > > Subject: [DUG] Another debugging question > > > > > > In my D7 Compiling options I have Runtime Errors Range, I/O and > > Overflow checking all turned ON. > > > > One site has reported a "Range Check Error" when running my > > application, on all their workstations. > > > > I cannot duplicate the problem on either of my developmemnt > > machines. > > > > Seems I have 2 options: > > Turn Range checking off in the compiler > > or track down the problem. > > > > Can anyone advise how to track down where the error is occurring > > since it doesn't give any address and I can't duplicate it here? > > > > TIA > > > > Mark > > _______________________________________________ > > Delphi mailing list > > [EMAIL PROTECTED] > > http://ns3.123.co.nz/mailman/listinfo/delphi > > _______________________________________________ > > Delphi mailing list > > [EMAIL PROTECTED] > > http://ns3.123.co.nz/mailman/listinfo/delphi > > > > > _______________________________________________ > Delphi mailing list > [EMAIL PROTECTED] > http://ns3.123.co.nz/mailman/listinfo/delphi > _______________________________________________ > Delphi mailing list > [EMAIL PROTECTED] > http://ns3.123.co.nz/mailman/listinfo/delphi > _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
