> I thought this was fixed when PR 11767 was fixed. Ouch! You're right, I should have done my homework :-) The problem was reported against a GCC 3.2.x based compiler. Glad to see I came to the same conclusion as Richard :-) Many thanks, Andrew, for your invaluable (and quick) feedback. -- Eric Botcazou