See the code sample below.
It just tried to rename the it variable in the inner loop, with the refactoring features.
The parser finds also any other it variables in the outer scope.
Is this by design and wanted?
for (TSET_IDS::iterator it=setUsed.begin(); it!=setUsed.end(); ++it)
{
// check if only used in one context or if we
// are about to delete this context.
const TSET_CTableContext &setContext = mapUsage[*it];
// We count how often this context is in use by the
bool bUsedOutSide = false;
for (TSET_CTableContext::const_iterator it=setContext.begin(); !bUsedOutSide && it!=setContext.end(); ++it)
{
if (it->m_lIdAS!=m_context.m_lIdAS ||
(m_context.m_lIdPJ!=0 && it->m_lIdPJ!=m_context.m_lIdPJ) ||
(m_context.m_lIdRL!=0 && it->m_lIdRL!=m_context.m_lIdRL))
{
bUsedOutSide = true;
break;
}
}
}
