IRC channel logs
2024-12-20.log
back to list of logs
<lechner>Hi, is there a way introspect the arity of a procedure, please? <jmes>What does it mean to be suspendable or not in guile? Must we handle SIGINT or something? <jmes>Context: Shepherd docs are talking about a "suspendable thunk" for an action of the new Timers feature. <jmes>lechner: There is a procedure called 'arity` that should do the trick <jmes>Is there any guile implementation of org.freedesktop.Notifications? <rlb>efraim: were you planning to try a bisection? <efraim>rlb: I can try to bisect, but I'm not sure if build failure I will run into will be because of big-endian or because of 32-bit. I might bisect 3.0.9 to 3.0.10 on i686 first and then see if those are still good on 32-bit powerpc <lechner>Hi, is there a way to exit debug frames without ",q"? Sometimes, I accidentally quit my Geiser session. Thanks! <lechner>Hi, is 'read-line' safe from buffer overflows? Thanks! <civodul>lechner: BTW, did you get replies re codeberg.org/guix? <lechner>Hi, why does Guile use GUILE_EXTENSIONS_PATH to locate shared libraries instead of the more common LIBRARY_PATH or LD_LIBRARY_PATH, please? <graywolf>Oh, #:autoload does not work together with #:re-export. Is that by design? <rlb>efraim: another thing I thought to try, given time, is if we jit on powerpc(?) and if there's an easy way to turn that off, see if that has an effect. (Also, of course, need to gdb it to try to see where it's crashing.) <graywolf>#:autoload does not work together with #:re-export. Is that by design? Would anyone know? <dsmith>lechner, Well, One possible reason is that a compiled Guile libxxx.so type extension really only makes sense for Guile, not some random C prog. <dsmith>And a guile .so type extension isn't required to start with "lib". <dsmith>lechner, For example, the simple sqlite interface for the bot is named "sqlite.so" <mwette>lechner: are you thinking one would put guile foo.so in lib/ or add the guile extensions dir to LD_LIBRARY_PATH; either option seems to have issues (littering lib/ w/ program-specifics or potentially having all programs looking in guile-specific so dirs) <mwette>Python .so's live under a python-specific dir and are found via PYTHONPATH <graywolf>I thought we have GUILE_EXTENSIONS_PATH for the same purpose <mwette>graywolf: we do; there was Q asking why that exists <graywolf>Ah I see, did not see beginign of the conversation