guile-pg 0.47 bug report
I just updated pkgsrc to 0.47. Three nits: You say to send bugs to ./configure --help, but that doesn't show up in the installed package anywhere. Tests failed (entirely) due to running out of shm segments. I have regular pgsql running, and I think the tests used to work. So I wonder if there is some newly expanded maxconnections in the test driver. There's a libpostgres.la symlink in $prefix/lib/guile-pg that wasn't there in 0.46, not mentioned in NEWS. It seems like it is extra and unnecessary. pgppPQJ1jZ1h3.pgp Description: PGP signature
GSOC: First update
Hi, As some of you will know, I am implementing a guile->js backend as part of Google Summer of Code. This is a small update so that those of you who do hang out on the guile irc channel can see some of the (small) progress. A temporary git branch is available at https://gitlab.com/ijp/guile/commits/compile-to-js I'm not going to list all the reasons you shouldn't use this code yet, suffice to say you shouldn't. It's so far before alpha it's not even funny. That said, code you can compile today includes multiple values [1], mutual recursion [2] and using call/cc to escape early from a loop [3]. 1. scheme: http://shift-reset.com/pastes/merge.html js: http://shift-reset.com/pastes/merge-js.html 2. scheme: http://shift-reset.com/pastes/even.html js: http://shift-reset.com/pastes/even-js.html 3. scheme: http://shift-reset.com/pastes/product.html js: http://shift-reset.com/pastes/product-js.html To make the examples self-contained and runnable in node.js, I included the code from module/language/js-il/runtime.js, assigned the result to a var and call console.log, and beautified it with uglifyjs for good measure. The actual output of "guild compile --to=javascript foo.scm" can be found between the comments. -- Ian Price -- shift-reset.com "Programming is like pinball. The reward for doing it well is the opportunity to do it again" - from "The Wizardy Compiled"
Re: my current project: new lalr module
On Sat, 2015-06-06 at 10:19 -0700, Matt Wette wrote:
> On Jun 4, 2015, at 1:41 AM, Nala Ginrut wrote:
> >
> >> 1) There is no specification of terminals. Terminals are detected in
> >> rules (via fenders) as quoted symbols or characters.
> >>Example of terminals: 'number, #\+
> >
> > hmm...and strings? Do you have plan to let users choose whether to use
> > terminals-inference? ;-)
>
> This I will think about. It should not be difficult. (I'm wondering what
> to do with strings like "(hello)" that I might want to convert to symbols.)
IIRC, this is implementation specific, say, #{\x28;hello\x29;}#
You can get it from string->symbol. And #{...}# notation is Guile
specific.
But you don't have to worry about the portability, since you may use
cond-expand.
Best regards.
Re: GSOC: First update
nice job! I've read the code very quickly, my understand is to convert CPS to plain JS code directly, right? Do you have a plan to generate it according to asm.js spec? On Sun, 2015-06-07 at 18:39 +0100, Ian Price wrote: > Hi, > > As some of you will know, I am implementing a guile->js backend as > part of Google Summer of Code. This is a small update so that those of > you who do hang out on the guile irc channel can see some of the > (small) progress. > > A temporary git branch is available at > https://gitlab.com/ijp/guile/commits/compile-to-js > > I'm not going to list all the reasons you shouldn't use this code yet, > suffice to say you shouldn't. It's so far before alpha it's not even > funny. > > That said, code you can compile today includes multiple values [1], > mutual recursion [2] and using call/cc to escape early from a > loop [3]. > > 1. scheme: http://shift-reset.com/pastes/merge.html >js: http://shift-reset.com/pastes/merge-js.html > > 2. scheme: http://shift-reset.com/pastes/even.html >js: http://shift-reset.com/pastes/even-js.html > > 3. scheme: http://shift-reset.com/pastes/product.html >js: http://shift-reset.com/pastes/product-js.html > > To make the examples self-contained and runnable in node.js, I > included the code from module/language/js-il/runtime.js, assigned the > result to a var and call console.log, and beautified it with uglifyjs > for good measure. The actual output of "guild compile --to=javascript > foo.scm" can be found between the comments. >
