4 ms·
I was impressed they switched to C11, since that's pretty cutting edge for a large C project. This commit[1] however shows that what they're actually using is
by unwind 10y ago
I was impressed they switched to C11, since that's pretty cutting edge for a large C project.
This commit[1] however shows that what they're actually using is GNU11, i.e. C11 with GNU extensions, since they seem to rely on those. I double-checked the most recent revision of the configure.ac file[2] and it seems to be still at GNU11.
Not complaining, but I think the changelog entry ("Changed the C standard from C99 to C11") is ever so slightly misleading.
[1] https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=dcbe79bd630b6176eac7214834234218de744f2a https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?i...
[2] https://cgit.freedesktop.org/pulseaudio/pulseaudio/tree/configure.ac https://cgit.freedesktop.org/pulseaudio/pulseaudio/tree/conf...
- CJefferson 10y agoUsing 'true' C99 is a bad idea, because the headers of many libraries don't work if you use -std=c11. gcc's default has always been the 'gnu' variant, so previously gnu90, now gnu99. I has similar problems when I switched from the default (at the time) C++03 to -std=c++11 and found unexpected things broke. I switched to -std=gnu++11 and everything was fine.
- fusiongyro 10y agoI glanced at the surrounding commits and I couldn't see the motivation for the change. Do you know what pushed them to use C11 or GNU11?