> I have corrected my code, but I thought you might like to know that the > way gcc handles this case isn't too graceful :) Thanks for your bug report. The mainline compiler (2.96 19991121 (experimental)) compiles this just fine, so it appears the bug has been fixed. Regards, Martin