[jm47048]

Originally Posted by The Wolf

This is simply utter nonsense. Bug-free software exists. Businesses have been running numerous bug-free COBOL programs for decades. There are many examples of it. Claiming it doesn't exist is just silly. Heck, companies even make development tools for creating it.

Escher Technologies - Products - Bug-free Software

And wht if there are bugs in the tool you describe in this link above? Read this below from a Wikipedia article that has valid scientific citations (not corporate advertising). I have said my peace, but please... if you're going to comment on software development, please educate yourself. I am not going to fight about it, but the fact doesn't change just because you post a link to some corporate product no one has ever heard of that tells me they promise my software will be bug free. That is arrogant of them.

To see the full article, please go here:

Software bug - Wikipedia, the free encyclopedia

Bug management
It is common practice for software to be released with known bugs that are considered non-critical. While software products contain an unknown number of unknown bugs when shipped, measurements during the testing may provide a statistically reliable estimate of the number of likely bugs remaining. Most big software projects maintain a list of "known bugs". This list inform users about bugs that are not fixed in the current release, or not fixed at all, and often a workaround is offered additionally.
There are various reasons for such a list:

• The developers often don't have time to fix all non-severe bugs.
• The bug could be fixed in a new version or patch that is not yet released.
• The changes to the code required to fix the bug would be large, and would bring with them the chance of introducing other bugs into the system.

Given the above, it is often considered impossible to write completely bug-free software of any real complexity. So bugs are categorized by severity, and low-severity non-critical bugs are tolerated, as they do not impact the proper operation of the system, for the majority of users. NASA's SATC managed to reduce number of errors to fewer than 0.1 per 1000 lines of code (SLOC) but this was not felt to be feasible for any real world projects.
One school of thought, popularized by Eric S. Raymond as Linus's Law in his essay The Cathedral and the Bazaar, holds that popular open-source software holds a better chance of having few or no bugs than other software, because "given enough eyeballs, all bugs are shallow".<SUP class=reference id=cite_ref-10>[11]</SUP> This assertion has been disputed, however: computer security specialist Elias Levy wrote that "it is easy to hide vulnerabilities in complex, little understood and undocumented source code," because, "even if people are reviewing the code, that doesn't mean they're qualified to do so."<SUP class=reference id=cite_ref-11>[12]</SUP>