So, "no docs, no bugs" ?
Yes. And no.

If you try to define rigorously what a bug is, you don't really have a choice.

However normally the documentation isn't really rigorous either. The manpage for grep say it searches for matches of regular expressions - but it doesn't say that it terminates after all input is exhausted. Normally you'd still say it's a bug if it hangs afterwards.

But you can't just say that every program has to terminate, because stuff like servers often has to run until stopped by external intervention.

So strictly speaken "no docs, no bugs" holds true. But you can still disappoint the user, and in some cases people will call that a "bug" as well.

I'll remember that for next time I need a good excuse for not having written documentation ;)

When you write software for money, you usually have some kind of requirement docs, which serve as docs as well. If not, you're lucky.

(I saw that smiley, yes, but I still wanted to express my thoughts about what a bug is and what not).

In reply to Re^3: Bug or WAD in lvalue substr? (What is a bug anyway?) by moritz
in thread Bug or WAD in lvalue substr? (again.) by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.