IRC channel logs

2018-01-09.log

back to list of logs

<amz3>so gnunet-guile works as expected with taylan patch
<amz3>to guile-bytestructures
<amz3>ACTION sent a new package to guix
<amz3>now, I just need to manually go through hundreds of definitions in gnunet headers and bind what is missing ie. most of it
<amz3>louishaemmerle: I debug with 'pk'
<louishaemmerle>amz3, what is 'pk'?
***ota_ is now known as ota
<amz3>logicmoo:
<amz3>sorry
<cehteh>:D
<amz3>héllo all
<manumanumanu>Hallå all!
<ZombieChicken>Is there a logic programming module for Guile out there? Something like Prolog?
<civodul>ZombieChicken: minikanren!
<ft>Does minikanren run on Guile maybe?
<civodul>there's a Guix package, even
<ZombieChicken>I don't run Guix
<manumanumanu>Hmmm. I am having some problems using pointer->procedure. I am writing a scheme FFI binding for libsodium, which sadly has me dabbling a bit with memory allocation. I am trying to make a binding to sodium_malloc, which is a memory-protected version of malloc that instantly kills any application trying to read too far (or before the memory region).
<manumanumanu>making a correct binding to sodium_malloc is easy (the same as malloc), however, running it from guile immediately kills guile
<manumanumanu>so guile must be doing something wonky with with the memory
<manumanumanu>if any of you have libsodium installed, you can try this: https://pastebin.com/8Np72eFj
<manumanumanu>I don't know how guile handles external memory pointers, but that behaviour seems a bit weird
<manumanumanu>I have tried passing it sodium-free as a finalizer using make-pointer, but it still coredumps
<dsmith-work>Tuesday Greetings, Guilers
<amz3>o/
<amz3>ZombieChicken: I use this fork of microkanren that runs on guile https://framagit.org/a-guile-mind/guile-wiredtiger/blob/master/microkanren.scm
<wingo>moo
<ZombieChicken>amz3: Someone on #prolog pointed me to something else that I think will do the job, but thanks for the link.
<ZombieChicken>though I do like one file solutions to problems. Hmm
<ft>ZombieChicken: what did they point you to?
<ZombieChicken>guile-log, I think
<ZombieChicken>I'm not sure I'll be using it tbh
<ZombieChicken>it was mostly a 'just in case' kind of thing
<amz3>ZombieChicken: well, if you do something useful with minikaren, microkanren or guile-log don't forget to post it to the mailling list please
<amz3>I am very interested
<amz3>myself I use microkanren to do recursive queries of a feature space
<ZombieChicken>I'm just trying to start piecing together a design for a chat client
<ZombieChicken>because I'm sick of the options out there right now
<amz3>chat client? how is that related to logic?
<ZombieChicken>That's part of the reason I was looking for options. Once I figure out about how I want to try something, I want to know if I have the tools to do it
<amz3>ZombieChicken: I build a database is scheme that you can query in microkanren
<amz3>I mean it rely on a C library
<amz3>but the interface is guile
<stis>heya guilers!
<manumanumanu>stis: ahoy!
<manumanumanu>What is going down in GoT-town?
<stis>slow times, slow times, not much, som physics play with math and theory
<manumanumanu>What weather we have in Sweden these days. It lends itself well to programming
<ijp>I dunno, I'm not much further south, and I'm just sick fed up of looking at computer screens
<manumanumanu>I am rained in
<ijp>although I'm writing maths not code
<manumanumanu>what options for the built in FFI are there?
<ArneBab_>amz3: is there a simple tutorial for microkanren in Guile?
<amz3>ArneBab_: no :/
<amz3>manumanumanu: "for the built" ? what is that?
<manumanumanu>amz3: : for the built-in ffi
<dsmith-work>amz3: "built in" as in "the one included with guile"
<manumanumanu>the whole thing bytevector->pointer gets annoying.
<manumanumanu>I'm used to how chez does it, which can do implicit string and bytevector -> pointer conversions
<spk121>manumanumanu: I did use the vanilla Guile FFI once, in this thing https://github.com/spk121/guile-aspell/blob/master/aspell.scm
<spk121>I approached it as is a two-layer problem. A binding that is close to the C API, and then scheme functions that abstract them
<spk121>But I haven't touched the FFI since that one attempt.
<civodul>heya spk121 :-)
<amz3>manumanumanu: I don't get it, you have to convert scheme types to types understood by guile ffi explicitly if that what you find annoying
<spk121>hi civodul
<civodul>spk121: are you coming to FOSDEM this year?
<spk121>civodul: It seems likely, but, I haven't bought a ticket yet. But, I don't have anything to demo or brag about. ;-)
<civodul>heheh, chatting and all is fine though :-)
<spk121_>civodul: My New Year's Resolution for 2018 is to only finish projects in my back catalog, and to not start new projects.
***spk121_ is now known as spk121
<civodul>yeah that's what we always say ;-)
<civodul>the number of stashes and branches in my guix checkout keeps growing
<spk121>civodul: haha. There are about four unfinished Guile applications, plus about four C++ and 1 in PHP, so if I finish one per month...
***logicmoo is now known as dmiles