John Beck wrote:
> JohnS> ... I was under the impression that code should
> JohnS> never make reference to the bug it fixes. Am I mistaken here?
> No, you are quite correct. Referring to an open bug e.g.:
> * Work around silly misfeature until 6999999 is fixed.
> is OK, but the comment proposed in this case is not. Something like:
> * Allocate one extra array entry to keep gcc happy.
> should suffice.
Is the new webrev
Ok for you ? It refernces an open bug instead of the one used for the
__ . . __
(o.\ \/ /.o) roland.mainz at nrubsig.org
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 3992797
(;O/ \/ \O;)