@rootkea I'm not asking if the volatile is needed with current Glib, I know volatile is useless between threads.
As you said the volatile is still in the function definition in recentish Glib versions (2.64 from Ubuntu LTS for eg) but its gone from the docs for Glib 2.70, don't know about the code. What I'm asking is will removing it on our variable make compilers complain the opposite way because the volatile is still on the function prototype? I know in C++ its UB to pass a non-volatile to a volatile, but C may be ok. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/2907#issuecomment-927560010
