--- In AVR-Chat@yahoogroups.com, "arhodes19044" <spamiam@c...> wrote: > Of course you are right. No, he isn't. To call a bug a feature just because it is documented is to destroy the distinction between functionality that is useful to the user and functionality that is detrimental. For example, the defect in Microsoft Word whereby the "space before" of a paragraph is not supressed at the top of a page after a manual page break must be approaching its tenth birthday. It has been documented for a long time. But, nobody wants Word to work that way. Calling it a feature is just playing with words. It is a defect, or, if you have to use the word, a bug. You could usefully call it a "known bug" to distinguish it from defects introduced recently that are not yet accepted as just another mine in the minefield. There are also "bad design decisions". Maybe that's what we have here. One could wish for things to be otherwise, but, pragmatically, having the thing documented is the best you can hope for. Graham.
Message
Re: documentation of timer interrupts vs bugs
2005-04-22 by Graham Davies
Attachments
- No local attachments were found for this message.