IRC channel logs
2018-01-30.log
back to list of logs
<spk121>wingo: the procedure module-remove! is undocumented. OK to use it? <ijp>spk121: I would expect so, although maybe the best thing would be to document it :) <ijp>I don't think the module api is going to change much <ijp>or rather I hope not, because it'll be a pain if it does <spk121>ijp: I guess that it would be pretty stable. On the other hand, removing things from modules isn't common. <ijp>yeah, I think I've done it maybe once <markx>What's the recommended way to install guile libs on mac os? <amz3>so using threads with gnunet is not "legal", I need to embedded gnunet loop inside guile-fibers <ArneBab_>amz3: could you use single-threaded fibers instead - and just not use threads? <amz3>Single thread fibers won't help because the issue is that gnunet takes the control of the thread <amz3>right now, I run gnunet in another thread <amz3>but it doesn't have somekind of "inbox" so that I can push to the gnunet event loop, new tasks <amz3>the other solution, is to avoid the gnunet event loop <amz3>or to wake up the gnunet event loop every 1 sec for instance, to read its inbox <amz3>well, I think I will just avoid the gnunet event loop <amz3>it will be better in terms of performance i think <daviid>amz3: another possibility would be to read guile-async2 code (the part that integrate with glib loop), then write a guile-async2 branch that would do the same but using the gnunet loop (or emulate what guile-async2 does using fibers...) not trivial of course but ... <amz3>daviid: yes, I should look guile-async2, tx.