<civodul>so many game frameworks in Guile! :-) <davexunit>mark_weaver: is what you posted on the ML awhile ago the most recent version of the mvars module? <mark_weaver>iirc, I posted two versions. make sure it's the later one. <mark_weaver>it's not a commit; just the file. I'm not sure I ever made it into a commit. <davexunit>my patch will just assume that (ice-9 mvars) is there and if/when it gets a new name we can change it. <mark_weaver>Thanks! I'm overwhelmed with things to do for Guile, so if you could help get this REPL thing done, it would be much appreciated :) <davexunit>whoa markwiter showed up! stay awhile next time... <davexunit>mark_weaver: so with this new repl patch, we want to avoid that read-wrapper stuff that we did before, right? <davexunit>this should be done without adding a new REPL option. <mark_weaver>I'm concerned that the read-wrapper exposes an API that we might regret later. <mark_weaver>however, it might be reasonable to use something like that internally, dunno. <davexunit>okay. I'll need to generalize a thing or two. finding the best places to do so is the tricky part. <davexunit>perhaps run-repl can take a reader proc which is prompting-meta-read by default, that way I can insert my own wrapper around it. <mark_weaver>that makes me a little nervous since run-repl is exported. <mark_weaver>maybe rename the existing 'run-repl' to something else that's not exported, and then make 'run-repl' just call the new internal procedure with 'prompting-meta-read' as an argument? <davexunit>then I'd need to write another procedure that calls the internal procedure with a new reader. <mark_weaver>well, I think it would be okay to call it using the (@@ <module> <id>) syntax. <mark_weaver>or to make the code a little nicer, do something like (define run-repl* (@@ (system repl repl) run-repl*)) <davexunit>okay. that seems a little strange to me, but I guess it's okay since we really don't want to expose the procedure publicly. <mark_weaver>but unfortunately in this case we need two modules to cooperate behind the scenes without exporting the private interfaces between them. <davexunit>getting this to work with the (system repl server) module will be even more fun, heh. <dje42>Am I correct in saying strings in Guile don't have an encoding. Reading/writing strings requires an encoding of course. <dje42>e.g. If I have a Scheme function that returns a string, do I need to specify what the encoding of the result is? <mark_weaver>in Guile 2, strings are sequences of unicode code points. <dje42>That's what I thought. Cool, thanks! <tromey>congratulations on your /. article wingo <davexunit>awful slashdot comments. why am I not surprised? <tromey>me too, so for my sanity I rarely read comments <tromey>life's too short for all that crap <davexunit>if only I had your decision making skills :P <davexunit>wingo's article was above my level of understanding, but I did learn a bit about what CPS is. <davexunit>I couldn't use the API, but I have a better idea of what it does and why. <wingo>i don't expect anything from comments, so it's all amusing <wingo>i just finished updating docs for the new compiler btw, so in master it's all part of the "Guile Implementation" section <davexunit>searching slashdot for "wingo" gets you there. <wingo>i don't plan on touching that much more at this point, need to focus on a release <wingo>main missing thing is NEWS now *wingo looking at lloda's thing today also :) <ArneBab>wingo: I’m currently writing an article on my path from python to guile. Would you be able to do a review on its readability when I’m finished? I ask you, because your article are mostly a joy to read, so I hope that you can find the places where I need blow dust from my text ☺ <ArneBab>is there a way to use FFI with fortran? ***jao is now known as Guest80122
<ArneBab>can (dynamic-link ...) link to C++ libraries? I tried linking libstdc++ and it fails with file-not-found: (define libstd (dynamic-link "/usr/lib/libstdc++.so.5")) <dsmith-work>Whee. The guile manual is now at 900 pages. With the TOC spanning 20 pages. <ggrant>davexunit: Yah, mwitmer committed your fix! :^) *ggrant was thinking of seeing if he had some free-time this weekend to start a *.texi ... looking like it might be a better goal for next-week, by the look of it thusfar.