If a product is alleged to have feature X

Alleged? By whom? When? On what basis? And whom alleges that someone alleged that the product had this feature?

The problem with not intelligently differentiating between missing features and bugs, is that it makes it impossible to prioritise properly.

A bug is (should be) a higher priority than a missing feature. It is something that prevents an implemented feature from being useful until it is fixed.

A missing feature is lower priority because if the bugs in the implemented code are fixed, a less featured product may still be useful and shippable.

And that pretty much addresses your "dependant feature" argument. If an implemented feature doesn't work without an unimplemented feature, then both are miss-categorised. The dependent isn't complete, so is not yet an implemented feature. And the dependency is not a feature, but an unimplemented subset of the dependant feature's functionality.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^12: regexp class (no bugs) by BrowserUk
in thread re: regexp class by Anonymous Monk

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.