Conversation

Notices

1. Embed this notice
   nyanide :nyancat_rainbow::nyancat_body::nyancat_face: (nyanide@lab.nyanide.com)'s status on Saturday, 24-May-2025 03:15:45 JST nyanide :nyancat_rainbow::nyancat_body::nyancat_face:
   so apparently sleep is MT-Unsafe and this doesn't really help me to know when I shouldn't call it
   • Embed this notice
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: (nyanide@lab.nyanide.com)'s status on Saturday, 24-May-2025 03:17:49 JST nyanide :nyancat_rainbow::nyancat_body::nyancat_face:

     in reply to

     • ロミンちゃん
     @romin if this were 1983 this would be helpful but uh, processors are really fast.
   • Embed this notice
     ロミンちゃん (romin@shitposter.world)'s status on Saturday, 24-May-2025 03:17:50 JST ロミンちゃん

     in reply to
     @nyanide just use a for loop
   • Embed this notice
     ロミンちゃん (romin@shitposter.world)'s status on Saturday, 24-May-2025 03:19:59 JST ロミンちゃん

     in reply to
     @nyanide loop harder
   • Embed this notice
     Daniel Stevens (eris@p.enes.lv)'s status on Saturday, 24-May-2025 03:20:08 JST Daniel Stevens

     in reply to
     Compared to sleep(3) and usleep(3), nanosleep(2) has the following advantages: it provides a higher resolution for specifying the sleep interval; POSIX.1 explicitly specifies that it does not interact with signals; and it makes the task of resuming a sleep that has been interrupted by a signal handler easier
     
     
     
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: likes this.