|
Jim, Jim Langston wrote: > You miss the point, Jeff. You don't have to prove there > are no bugs, you just have to make sure it has to bugs. How do you do that? (seriously). How do you "make sure" without proving? I think that you're missing the point here Jim (and it's a _very_ important one). You can't ever prove (or even "make sure") a program is bug free. You can only prove a program has bugs.... or fail to prove that it has bugs (which would be a good thing). > If a program always works and doesn't produce erroneous > data, that is by definition bug free. It works as advertised. "Always" is a lot longer than you're giving it credit for. jte P.S. Bug Admission: *NONE of my programs are Y10K compliant. :-)! -- John Earl johnearl@powertechgroup.com The PowerTech Group 206-575-0711 PowerLock Network Security www.400security.com The 400 School www.400school.com -- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.