Discussion on volatile

[weilin]

My computer education tells me your using gyroNow variable in separate task is not an asynchronous IO that requires volatile keyword.

My belief is that you do not need to use volatile because all V5 tasks are run on a single user CPU.

The PROS of PROS

I mean, VEXcode and VCS are also industry standard C and C++, it’s hard not to be when you use clang as the compiler and provide standard C and C++ libraries. PROS and VEXcode use different user APIs to access the V5 hardware, but underneath they are both using essentially the same SDK to access vexos. This is high level system architecture. [v5_system_arch]

@jpearman could be so kind to comment on this assumption.