On 23 October 2012 20:24, Thiago Macieira <thiago.macie...@intel.com> wrote: > > 1) volatile wasn't designed for threading. > > It was designed for memory-mapped I/O
Going slightly off topic, I never managed to find reliable sources about which problem volatile was meant to solve when it was *first* introduced: MMIO, changing values from signal handlers (together with a sig_atomic_t), or saving the value of automatic variables across a setjmp/longjmp? Of course now it's a reliable solution to all three problems... (Yes, threads never entered the picture.) Cheers, -- Giuseppe D'Angelo _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest