IRC channel logs
2025-10-29.log
back to list of logs
<rlb>Oh, good -- not sure what they were referring to, but if it's just "apt update", you can run that any time you like (usually, i.e. at least in debian that's fine). <mwette>kinda weird. yesterday nothing, today everything is there. I'm off to play. <apteryx>is using n-par-for-each unsafe when inovoking (via system*) commands that output to stdout? <apteryx>The issue would be sharing the same Guile port without mutexes <apteryx>but perhaps since the commands fork it's fine? <kestrelwx>I didn't consider that I'd have to take care of them. <rgherdt>hmm, I see. But I don't see that as a problem with the parsing library, right? Does that work in hoot? If not, one way to deal with it would be to define several foreigns that call "readPixels" with different arguments or something like that <sneek>tohoyn, you have 3 messages! <sneek>tohoyn, daviid says: this has nothing to do with g-golf, those warnings are being emited by the low level renderer you (or the system) choosed to render ... I'll ask for some hint in #gtk, but I can't promiss I'll get an answer <sneek>tohoyn, daviid says: can you launch the search-bar example, then hit Ctrl-Shitf-i, then in the inspector, go to the upper object (the GtkPaplicationWindow), then select the Global (header bar tab), then scroll down to the GL Renderer related entires, take a screenshot and posted somewhere, thanks <old>apteryx: have you tried object attributes instead of a global weak hash map for your mmap implementation? <sam113101>the other day I was reading an introduction on scheme and they were defining a "when" form/macro and a "for" one (kind of like a for loop), does the standard library have anything like that? <sam113101>I understand the language itself is trying to be minimalist <kestrelwx>sam113101: It does have `when` and there are looping constructs, you can look it up in Guile docs. <identity>sam113101: you generally use ‘map’ for a ‘for’ loop <sam113101>"it actually supports several languages, not just Scheme.", really? <lloda>current guile supports scheme, elisp, js, and brainfuck <lloda>i've only ever used scheme, but my understanding is that elisp support has some gaps and js lots <lloda>you can try them with $GUILE --language=... <sam113101>"Other supported languages are Emacs Lisp, ECMAScript (commonly known as Javascript) and Brainfuck, and work is under discussion for Lua, Ruby and Python." <identity>«integers.c:147: assertion failed» is a new one. i manage to break guile in new and exciting ways <mwette>I just tried these and something is a bit flaky. They worked a while ago. <identity>(expt 2 (expt 2 50)) specifically seems to trigger an assertion failure <identity>numbers much larger (like 100) raise a numerical overflow exception, while numbers lower than (excluding) ~40 compute as normal <ArneBab>sneek: later tell jralls: my concern with scm_from_unsigned_integer is just that I don’t know enough about the details, so I’m left asking about stuff that isn’t obvious to me to be correct. Please get in contact with Jonas to get to the heart of those issues. <dsmith>There are also a lua on Guile, IIRC