Hi, I don't think depending on gcc 4.1 without really understanding the issue is a good idea. There is a good chance that the bug is not really fixed, but only hidden by circumstances. So it would really be the best way to go to extract a minimal test case, see whether it's gcc's or tagcoll's fault, and then make sure it is really fixed.
--
Falk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
