Mark Howard wrote:
It's got me wondering how important it is to track down: should I just leave Range Checking off - given that (with it on) I won't know about a problem until a client complains: and then I can 'fix' it by turning Range checking off?ISTM that you should have it on, it is providing information,
without which you've got a lovely silent failure.
Its the error that is your problem, not the reporting of it.
If you are trying to set field (i) to be the dollars owed and i=-1
then, yeah, its probably reasonably important. If you are trying to
read the 20th line of a 19 line file, maybe not so important.
You should be able to narrow it down a fair bit just by stepping
through, or reading your code. Think most places error checking'll bite
you are places it be handled anyway - non/negative ints and
dates have both been mentioned, to which I'd add look out for arrays accessed from 0..n.
Although if its in a 3rd Party lib, you're prolly screwed...
Cheers, Kurt.
---------------------------------------------------------------------------
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/
