On 04/10/2012 06:53 PM, Timothy Pearson wrote:
I think I see the problem, but haven't recompiled
to test if this idea
resolves it for sure.
It looks like for whatever reason gcc < 4.7 was't barfing when the new
"it" object was created within the scope of the existing "it"
object,
which was created within the for loop definition. Thus, gcc's new
behaviour is definitely correct.
The easiest fix is to replace all instances of
"TQListViewItemIterator it(d->listView);"
with
"TQListViewItemIterator it2(d->listView);"
or similar.
Thank you Tim!
I'll give it a go and report back.
--
David C. Rankin, J.D.,P.E.