A bug is bug because it creates an unexpected behaviour which differs from the documentation.Sillyness.
Suppose you have a routine like this in your company's application.
Now someone files a bug report, the application dies with a divide by zero error, and the line number the bug happens is in this subroutine.# Calculate the average by adding the parameters and # dividing them by the number of elements. sub avg { my $sum = 0; $sum += $_ for @_; return $sum / @_; }
Now, you think you get high marks on your end-of-the-year review if you close this report with "Not a bug, the behaviour of the routine matches its documentation"?
Of course, there are many bugs because the code differs from the documentation. But bugs don't disappear just because the documentation matches the code.
Now, if you had said "you cannot have a bug if the code matches the specification", you may have something to argue (but even that is something I don't agree with).
In reply to Re^6: An Introduction to Literate Programming with perlWEB
by JavaFan
in thread An Introduction to Literate Programming with perlWEB
by adamcrussell
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |