Rule 10.1.2: Justification for considering volatile member functions as inappropriate

[misra cpp]

While we agree that the mechanics of C++ require a member function to be
declared `volatile` in order for it to be called on a volatile object, MISRA's
intent is to make it clear that it is the member data that is volatile.


struct Data
   {
    int i;
    int j;
   };

struct UseData
   {
    int getData() const {
        return m_data->i;
       }

    Data volatile * m_data;
   };