Post AzuoaopWRhLpZAYyyO by leah@blahaj.social
 (DIR) More posts by leah@blahaj.social
 (DIR) Post #Azuo0vkzDMfOcmKRUm by jleedev@mastodon.sdf.org
       2025-11-04T21:55:43Z
       
       0 likes, 0 repeats
       
       @ska Today I learned that signal.h is built with macros, and Python dutifully builds its signal module by checking them all with a series of ifdefs.
       
 (DIR) Post #Azuo0wjbZz9jemgqyu by lanodan@queer.hacktivis.me
       2025-11-04T22:05:03.058577Z
       
       0 likes, 0 repeats
       
       @jleedev @ska Yeah sig2str() and str2sig() only got introduced in POSIX.1-2024 (which is still too recent to rely on without checking) so you end up with piles of C macros in most codebases.
       
 (DIR) Post #AzuoaopWRhLpZAYyyO by leah@blahaj.social
       2025-11-04T20:51:14Z
       
       0 likes, 0 repeats
       
       @ska kill -5 is undefined ala POSIX, but tbh if it doesn't work I'd blame the implementation. :)
       
 (DIR) Post #AzuoapX7paEHkOxnw8 by lanodan@queer.hacktivis.me
       2025-11-04T22:11:31.126986Z
       
       0 likes, 0 repeats
       
       @leah @ska And sadly no rationale why -signal_number isn't mapped to kill() instead, which takes an int anyway so no chance of it being anything else, plus -signal_number is XSI shaded.
       
 (DIR) Post #AzurIPQeRobhR5qLL6 by lanodan@queer.hacktivis.me
       2025-11-04T22:41:50.363729Z
       
       0 likes, 0 repeats
       
       @ska @leah True that said -signal_number exists for a handful of standardized signals which 5 isn't part of.cf. https://pubs.opengroup.org/onlinepubs/9799919799/utilities/kill.html