|
> From: Wills, Mike N. (TC) > > That was my next plan... Yup. You've got the idea. Debugging is basically just tedious, step-by-step work. And the dirty little secret is this: the only reason I'm good at debugging is because I've made so many programming errors in my career <grin>. So, I've built a sort of mental catalog of places to look, based on my particular programming practices and mistakes I've made in the past. Once you solve this one, it'll be in your repertoire, and the next time you run across it you'll have a little head start. Me, I've got a big ol' list of Pluta's Poor Programming Practices, and so I can usually spot my mistakes pretty quickly. Even so, I make brand new ones all the time. My last one was trying to access buffer fields in a COBOL program without opening the associated file. COBOL doesn't find that amusing at all. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.