Robin Cornelius wrote: > The solution in this case may be (if gcc allows) to suppress the > specific warning? Yep, I think so. I have g++-4.2 now on Ubuntu, so I should be able to cook something up for this. <b