Defect reports?
Phil Edwards
phil@codesourcery.com
Thu Sep 25 05:19:00 GMT 2003
On Wed, Sep 24, 2003 at 09:08:26PM +0200, Gabriel Dos Reis wrote:
> P?tur Run?lfsson <peturr02@ru.is> writes:
>
> | I'm wondering what should be done about potential defect reports
> | discussed on this list over the last few months, most of which are
> | about streamoff, fpos<> and mbstate_t. Posting here doesn't seem
> | sufficient :-)
>
> (1) post them to news:comp.std.c++ -- they are automatically
> forwarded to the committee
> (2) appoint one of austern, bkoz, gdr to keep track of them and
> submit proper DRs.
> (3) contact your national body
> (4) koint the committee
> ...
5) Track defect-related changes specific to libstdc++ in
docs/html/ext/*.html.
--
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
- Brian W. Kernighan
More information about the Libstdc++
mailing list