On 09/17/17 13:07, Emil Velikov wrote:
Having the opposite - a destructor [1] should provide symmetry and consistency.
Furthermore using atexit is not as portable/reliable as one would think.
It should be the destructor that handles this. Either the user clears
it, or destructor clears it.
All this is obviously orthogonal to the original issue reported;-)
I don't see how it is orthogonal.
There is actually |__attribute__((destructor))
https://phoxis.org/2011/04/27/c-language-constructors-and-destructors-with-gcc
It works with gcc and clang, and probably with most or all other compilers.
|
Yuri
_______________________________________________
Pixman mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/pixman
