Conversation

Notices

1. Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Sunday, 03-Apr-2022 10:03:19 UTC Santa Claes 🇸🇪🇭🇰🎅

   in reply to

   • Haelwenn /элвэн/ :triskell:
   • epoch
   @lanodan @epoch @alexandra Or, as I would phrase it:
   
   aaaaaaaa
   • Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Sunday, 03-Apr-2022 10:03:20 UTC Haelwenn /элвэн/ :triskell:

     in reply to

     • epoch
     @epoch @alexandra uuuh, that's the kind of stuff I could expect on assembly but I find that ugly in C.
   • epoch@tilde.zone's status on Sunday, 03-Apr-2022 10:03:21 UTC epoch

     in reply to

     • Haelwenn /элвэн/ :triskell:

     @lanodan @alexandra
     on little-endian machines I've used a short to store the return value of fgetc then use the short's address as a char * since the next byte in memory is a \x00 unless fgetc returned an error.

   • Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Sunday, 03-Apr-2022 10:03:22 UTC Haelwenn /элвэн/ :triskell:
     @alexandra Oooh right, yeah, I have written code like that in C few times.
     Usually because well, C mindset and it's nice for things like checking (mostly) text-based magic numbers.