<koz_>Hi everyone! Is there anyone around with whom I can discuss some non-technical stuff related to Guile (and Scheme in general) over PM? I mostly seek advice. <daviid>how much time we can loose because of stupid things: trying to send an email to imagej@list.nih.gov and it has been refused twice>: (1) because it had a (kawa) scheme snipset attached and (2) because: "Your posting to the IMAGEJ list has been rejected because it contains an attachment of type 'APPLICATION/PGP-SIGNATURE'. The IMAGEJ list has been configured to reject such attachments. Please contact the list owner at <daviid>IMAGEJ-request@LIST.NIH.GOV for more information." <daviid>how is that: emails to gov lists refused because there are signed ?!? <koz_>daviid: Stupid corporate FUD? <koz_>\\query daviid Would you be OK to answer some Guile-and-Scheme-related questions? <davexunit>ACTION downloads the full SICP lecture series <daviid>ACTION is working on Guile-Clutter's new web-pages <daviid>davexunit: guile-squee is fully autotool chained, just need to do the git house keeping and push <adhoc>koz_: sometimes you just need to patience. <koz_>adhoc: Lol, I'm bad at patience. <daviid>davexunit: yea, I'm happy I found a bit of time, including it has a manual mockup and make distcheck pass <daviid>then I swtiched on 2 other projects, but this week I should finalize the git house keeping and push to evel <adhoc>koz_: as you can see its a small and busy community. <adhoc>koz_: this is also a quite time of day ***__uu__ is now known as __uu
<ArneBab>amz3: when is great, yes! (I also only discovered it after a few months, and it made quite a few things easier. Nowadays I mostly use cond, though) <ArneBab>daviid: I had people complain because their yahoo email was slow when I attached GPG signatures… <amz3>nalaginrut: what about serializable continuation :)) <nalaginrut>amz3: well, that one will be discussed after 0.2 <amz3>ArneBab: hey I saw your message. The thing is that I'm really too busy with my current project which boils down to create a clone of opencog <amz3>If I fail or get bored I make sure to ahve a look at freenet <amz3>well, it's not really a clone since there is so many thing in opencog ***wlhlm1 is now known as wlhlm
<amz3>let's say I study opencog <taylanub>davexunit: you still have a Gitorious link under "Social" BTW <taylanub>ACTION submitted to GitHub after all :\\ <davexunit>I self-host now. no mailing lists or bug tracker, though. <taylanub>wlhlm: it seemed like you guys were somewhat farther in the debugging yesterday, and I didn't have much time... are we positive that the unloading is even supported by Guile? in any case I can try it tomorrow, sorry for delaying. <taylanub>now that I read that page in full, it looks like it crashes before the dlclose() call, so that's not it I guess. (I only skimmed over the discussion here yesterday.) <taylanub>actually I'm not sure how much time I'll have tomorrow either, though the instructions seem pretty straightforward so I guess it won't be a problem <taylanub>wlhlm: looking at the logs from yesterday .. you said twice that it segfaults on unload, but "Closing Guile... " isn't in the output, so doesn't it segfault in the call to init_func() already? <daviid>OT ArneBab: wrt signing email, not being able to sign emails to the imagej.gov list was a bug in their config, I wrote to the ML maintainers and they now fixed it <wlhlm>taylanub: No problem, I just wanted to see if this happens on other machines or if my setup is broken in some weird way. <sam4>Hi, so I have a bit of a wierd problem. I'm writing an n body simulator in C with SDL2 and I want to use guile to do the logic but it needs to run in a seperate loop from the SDL rendering loop and I don't really know how I'd pass data in between the two. I just need somebody to point me in the right direction, thanks. <taylanub>wlhlm: ah, there's no newline at the end of "Closing guile... " so I guess it doesn't flush the output, or something <wlhlm>taylanub: From the dynamic loader debug info, it looks like the problem gets triggered when it tries to remove libffi from memory. <wlhlm>So far, I haven't been able to isolate the problem yet, but I wonder whether it's worth it. Maybe the issue goes away with el capitan...