IRC channel logs

***ft_ is now known as ft

***serhart_ is now known as serhart

***karswell` is now known as karswell

<janneke>heading over to #fosdem

***mario-go` is now known as mario-goulart

<McDecaf>Are parameters like current-output-port contained to only the current thread or do they leak outside of it when using parameterize?

<paroneayea>woooo guile/guix room!

<paroneayea>whew! talks over :)

<jmd>How did it go?

<mark_weaver>McDecaf: parameters and fluids are thread-local variables.

<mark_weaver>when creating a new thread from guile, the spawned thread inherits the values of those variables from the parent thread, though.

***Guest71697 is now known as mikey

***mikey is now known as Guest53719

***Guest53719 is now known as mikey

<dakotafisher>I'm doing some research into logic programming and was wondering if anybody had the code for guile-log

<dakotafisher>I can find the manual, but am having trouble finding the actual source code

<OrangeShark>dakotafisher: this? https://gitlab.com/gule-log/guile-log

<dakotafisher>that seems to be it, thanks

<OrangeShark>here is a good list someone made of a bunch of guile projects http://sph.mn/content/3e73

<dakotafisher>thanks, that list is actually really helpful

<McDecaf>mark_weaver, yeah, I figured as much from the SRFI thread specification. So it is completely safe to work around the fact that open-pipe* just takes the current-output-port param by simply using paramaterize to change itand implement a vesion of open-pipe* which consumes both an input and output port as variable?

IRC channel logs

2016-01-30.log