Do non-static member variables in a C++ struct/class need to be marked as volatile to be treated as volatile in a member function?

by

Marking a member function volatile is like marking it const; it means that the receiver object is treated as though it were declared as a volatile T*. Consequentially, any reference to x or y will be treated as a volatile read in the member function. Moreover, a volatile object can only call volatile member functions.

That said, you may want to mark x and y volatile anyway if you really do want all accesses to them to be treated as volatile.

More Related Contents:

  1. When to use volatile with multi threading?
  2. Why is volatile not considered useful in multithreaded C or C++ programming?
  3. Operator overloading : member function vs. non-member function?
  4. What are all the member-functions created by compiler for a class? Does that happen all the time?
  5. Why do we use volatile keyword? [duplicate]
  6. Why does volatile exist?
  7. Volatile in C++11
  8. Effective C++ Item 23 Prefer non-member non-friend functions to member functions
  9. What kinds of optimizations does ‘volatile’ prevent in C++?
  10. Why does std::cout convert volatile pointers to bool?
  11. Does the C++ volatile keyword introduce a memory fence?
  12. Is volatile bool for thread control considered wrong?
  13. How to directly bind a member function to an std::function in Visual Studio 11?
  14. Why is the volatile qualifier used through out std::atomic?
  15. Does accessing a declared non-volatile object through a volatile reference/pointer confer volatile rules upon said accesses?
  16. Nonstatic member as a default argument of a nonstatic member function [duplicate]
  17. Print address of virtual member function
  18. Why is volatile deprecated in C++20?
  19. Why am I not provided with a default copy constructor from a volatile?
  20. Is it allowed for a compiler to optimize away a local volatile variable?
  21. C/C++: casting away volatile considered harmful?
  22. What Rules does compiler have to follow when dealing with volatile memory locations?
  23. Is ‘volatile’ needed in this multi-threaded C++ code?
  24. What is the meaning of ‘const’ at the end of a member function declaration?
  25. Free function versus member function
  26. Invalid operands to binary expression while implementing vector [closed]
  27. Difference between pointer and reference as thread parameter
  28. Why can we use `std::move` on a `const` object?
  29. cannot convert ‘std::basic_string’ to ‘const char*’ for argument ‘1’ to ‘int system(const char*)’
  30. How to use new std::byte type in places where old-style unsigned char is needed?

Leave a Comment