const related error from Intel and g++ compiler but not from VC8.0

[alishapal]

Hi there
So I am getting these error messages from Intel (v10) and g++ (v4.1.2) compilers respectively:

"error: the object has cv-qualifiers that are not compatible with the member function. object type is: const element"

"error: passing 'const Tetelement' as 'this' argument of 'void element:setID(long int)' discards qualifiers"

But the same code gets compiled using Microsfot VC8.0 compiler with no errors!

After a quick search, I figured that I need to make sure that I am not passing a const object to a non-const function/member.
To my knowledge I am not doing that, here is portion of my code that I think is relevant:

This is the part that invokes the error:

std::list<Tetelement> TetMesh::GetSortedElementList() {
int counter = 0;
std::set<Tetelement,Tetelm_less>::iteratorit;
    for (it=myelms.begin();it!=myelms.end();++it) {
        (*it).setID(++counter); // error line 
        this->sortedtetlist.push_back(*it);
    }
        return this->sortedtetlist;
}

Tetelement is a class derived from 'element' class in which 'setID()' is defined:

class element {
public:
// irrelevant code
      inline void setID(long int idn) { id = idn;}
private:
      long int id;
};
 
 
class Tetelement : public element {
// some code
};

As you can see 'it' iterator is _not_ defined as const_iterator and setID() is also a non-const member.

Now... the following change resolves the error in both compilers:

Tetelement temp_tet = *it;
temp_Tet.setID(counter);

So, is this related to how iterators are de-referenced under Intel and g++ compilers or Microsoft compiler is just ignoring my mistake and doing something behind the scene to fix the problem.

thanks for your time in advance :)

[weaknessforcats]

There are no errors. Older non-compliant compilers treat the members of a set container as const. set members are non-const. However, to change them, they need to be deleted and re-added. Otherwise the set structure is compromised.

When you add objects to a set, you can provide a key_compare object to compare keys. So long as you do not change the values of the set object used in the key_compare, you can update the set object. For this reason set objects are non-const.

[alishapal]

There are no errors. Older non-compliant compilers treat the members of a set container as const. set members are non-const. However, to change them, they need to be deleted and re-added. Otherwise the set structure is compromised.

When you add objects to a set, you can provide a key_compare object to compare keys. So long as you do not change the values of the set object used in the key_compare, you can update the set object. For this reason set objects are non-const.

Thanks for your very informative post.
SetID() function in the original post doesn't change anything that is being used by my key_compare object (Tet_less).
But this is kinda of annoying, now I can't use the same source code under different compilers :(

So would it be alright to assume that intel and g++ comilers are non-compliant ?

[weaknessforcats]

So would it be alright to assume that intel and g++ comilers are non-compliant ?

I am not a g++ expert, but I have heared that there is a -pedantic switch that forces ANSI compliance.

However, to a greater or lesser extent, all compilers are non-compliant.