| ??? 04/28/02 05:37 Read: times |
#22222 - Sleeping Bugs in the code: |
Hi,
The functioning of code in an application is merely a response to certain set of conditions. And the set of conditions is in fact one of the possible combination of various variables / inputs etc. One can debug the code if a combination or a stituation can be anticipated or is known. But not always you can visulize all combinations or situations, and those which slip away may contain a bug, which will strike you right when you are playing "time to market".... I know one answer to this can be, "PLAN YOUR CODE LAYOUT PROPERLY ON A PAPER" I request Gurus how do they manage while coding that no combination, situation or an eventuality skips their eyes. Or how do they ensure that no "sleeping" bug is there in the code when they deliver. Simon |
| Topic | Author | Date |
| Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: - more | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: - more | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: - more | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: - more | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: crash() | 01/01/70 00:00 | |
| RE: crash() | 01/01/70 00:00 | |
RE: Sleeping Bugs in the code: | 01/01/70 00:00 |



