Wrong function according to parameters is taken

[Lykurg]

Hi,

in my own model I have:

QVariant data(const QModelIndex &index, int role) const;
QVariant data(const QModelIndex &index, BibtexGlobal::SearchFilter role) const;
// BibtexGlobal::SearchFilter is an enum

QVariant data(const QModelIndex &index, int role) const;
QVariant data(const QModelIndex &index, BibtexGlobal::SearchFilter role) const;
// BibtexGlobal::SearchFilter is an enum

To copy to clipboard, switch view to plain text mode 

And in an other class I call:

QModelIndex index = sourceModel()->index(sourceRow, 0, sourceParent);
QHash<BibtexGlobal::SearchFilter, QRegExp*>::const_iterator i = m_filter.constBegin();
while (i != m_filter.constEnd())
{
  qWarning() << sourceModel()->data(index, i.key());
  ++i;
}

QModelIndex index = sourceModel()->index(sourceRow, 0, sourceParent);
QHash<BibtexGlobal::SearchFilter, QRegExp*>::const_iterator i = m_filter.constBegin();
while (i != m_filter.constEnd())
{
  qWarning() << sourceModel()->data(index, i.key());
  ++i;
}

To copy to clipboard, switch view to plain text mode 

But although i.key() is BibtexGlobal::SearchFilter the function data(const QModelIndex &index, int role) is called. Why? Is int and enum for the compiler the same?

Thanks

[Boron]

A pure enum is a simple signed int, according to the C and C++ standard.
Unless you make a "typedef enum", both functions will be the same for your compiler.

[Lykurg]

Unless you make a "typedef enum", both functions will be the same for your compiler.

Proofed and "no" (leastwise in my case), but don't ask me why, because I'm not an information scientist. The problem was, that sourceModel() referred to a QAbstractItemModel* which hasn't a member with BibtexGlobal::SearchFilter. After an const_cast to my model all worked as expected. Even without a typedef the correct function is called.

Thanks anyway

Lykurg

[wysota]

I wouldn't expect it to always work.

[Lykurg]

I wouldn't expect it to always work.

Depends on compiler/compiler version/plattform?

Currently I have changed the return value to a QString. Now - barring the original case - it should always work because the function has an other signature?

Thanks

[wysota]

Depends on compiler/compiler version/plattform?

Yeah, could be. I had a problem once when I had two variants of a method - one taking an int and one taking a string and when I was passing it const char *, it was always picking the int version because the conversion was "closer".