There was a problem fetching the pipeline summary.
use uint32_t to ensure alignment in union, improve comments
Loading
-
Just a remark: unsigned int will always be a 32 bit integer, on just about any conceivable system where Purr Data will be able to run on. I'm wondering, though, whether using uint32_t might be a portability issue. Are we guaranteed to include the proper headers so that it is available, on all Un*x platforms at least?
Edited by Albert Gräf
Please register or sign in to comment