Conversation

Notices

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 16-Jul-2025 07:29:40 JST Haelwenn /элвэн/ :triskell:

   • anna
   @ska @navi Well, unlike quite few C programmers I don't have a ${name}libs yet (and slightly want to avoid doing that but pretty sure I eventually will).
   • Embed this notice
     anna (navi@social.vlhl.dev)'s status on Wednesday, 16-Jul-2025 07:38:33 JST anna

     in reply to
     @lanodan @ska i also don't have my own personal catchall lib
     
     i also prefer to make smaller libs that can be packaged individually, and provide a set of utilities for a given topic, say a lib here for linear algebra math, or so on -- not a fan of "the one package with N libs under my name", it also helps that meson/muon lets me easily include what i need in a project as a subproject/wrap-file
     
     so far i've used strtol and kindof just... checked if endptr matched what i expected the string to be
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 16-Jul-2025 07:53:29 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • anna
     @navi @ska I think I'd also avoid a catchall, specially as one of my projects is a set of posix/unix-like utilities and so far I've avoided the "to compile these utilities, you need similar utilities pre-installed" trap. (With a little cheat, but still https://hacktivis.me/git/utils-std/file/bootstrap.mk.html )
     And a gigantic catchall library would just make bootstrapping harder to even broken (like if there's a ./configure script for the lib).