<daviid>tohoyn: yes, str1ngs is right,it has to be >= 3.0.7 <daviid>stis: great to count you among g-golf users, anything ... ping me ... or pinghere, others may help as well, there a few users here ... <stis>david, thanks, good to know *daviid is working to improve GI renaming so things lands in g-golf as they shoud ... i.e. g-list-model-get-item,not g-list-model-get-object, g-log-set-handler not g-log-set-handler-full ... about to nearly push a patch, finalizing... <stis>yey, just released stis-engine 0.1 <stis>I'm quite happy with the programmer interface now. <rlb>dsmith: I'm all in favor of more standardized regular expressions (not "whatever the platform does"). In lokke I just unconditionally depended on pcre... I didn't know about irregex. I wonder if there would there be perf concerns on non-jit architectures. <apteryx>dsmith-work thanks for the hintsights (re regexp in Guile) <apteryx>so something has been relaxed in the glibc to accept [0-9A-f] as a character range recently. <ArneBab>do you have an example of creating simple co-routines with call-withs-prompt? I’m currently writing websocket handling and I would like to run an output producer and only step back to the websocket handling when I need input. <ArneBab>Basically I want to create a soft-port that triggers parsing websocket input when I read from it ***sneek_ is now known as sneek
<ArneBab>(this is the long form for “help, I know what I want, but I don’t know what I’m doing” :-) <leoprikler>ArneBab I think you might want to set your co-routine up so that it takes the prompt as argument <leoprikler>then you can (abort-to-prompt prompt) on one side and on the other you can capture the continuation, set up the prompt again and continue whenever <leoprikler>though perhaps you might want to use SRFI 158 if you want to go fancier (don't know if a Guile implementation of that one exists, though) <mwette>ArneBab: look at run-scheduler in scheduler.scm in fibers