Such a quaint throwback!
〝volatile: The Multithreaded Programmer's Best Friend〞 — @incomputable
I'd forgotten how wild C++ was before C++11.
Don't do what the article says! An article from another era.
http://www.drdobbs.com/cpp/volatile-the-multithreaded-programmers-b/184403766 …
What are "volatile-qualified functions"? Do you mean member functions for working with volatile instances of a class? Or something else?
-
-
class Foo { void bar() volatile; };
-
Isn’t that just marking the this pointer volatile? I can think of some valid use cases for that.
-
No, it defines the member function to call if the this pointer is volatile.
-
So you’d overload it by providing another that isn’t volatile? Now that sounds straight up bizarre.
-
That’s been standard C++ forever. Same for const member function overloads.
-
Qualified proper-class types were always pretty nonsensical...
-
Don’t forget about ref and rvalue member functions! Much more to come
https://twitter.com/jfbastien/status/1004990262534426625?s=21 …
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
: void foo() 

;
C++31: void foo(void);