I've been considering writing a python compiler for guile. For python
(and others) there are several values considered to be false, such as
0 and various empty collections, and so a different approach will have
to be taken to this problem.
If we want guile to handle many different languages, shou
Hi,
Mark H Weaver writes:
> I've been considering writing a python compiler for guile. For python
> (and others) there are several values considered to be false, such as
> 0 and various empty collections, and so a different approach will have
> to be taken to this problem.
[...]
> So how abou
> With recent changes in guile vm there are lots on improvements on the
> Gambit benchmarks.
Improvements compared to what?
I should have been more concise.. I have run these benchmarks against
guile HEAD for some time (after I reported a few bugs, performance
regressions included, affecting
Hello,
l...@gnu.org (Ludovic Courtès) writes:
> The attached patch is an attempt to add unused variable reporting to the
> compiler, at the GLIL->assembly step. It was quite simple to implement
> here, and it should work with all front-ends (Scheme, ECMAScript, etc.),
> which is nice.
Following
Mark H Weaver writes:
> I've been considering writing a python compiler for guile.
Great!
> For python
> (and others) there are several values considered to be false, such as
> 0 and various empty collections, and so a different approach will have
> to be taken to this problem.
>
> If we want
l...@gnu.org (Ludovic Courtès) writes:
> Neil Jerram writes:
>
>> l...@gnu.org (Ludovic Courtès) writes:
>
>>> Maybe 1.8.7 is approaching now?
>>
>> Yes, that would be good. It might just be worth fixing the jmp_buf
>> definition problem before that (which I should get to in the next week
>> or
Hi!
Playing around with Guile's now-in-core syntax-case support (using Git
HEAD as of today), I found that quasisyntax seems quite broken:
(define-syntax test
(lambda (stx)
(syntax-case stx ()
((_ id body ...)
#`(let ((id #,(symbol->string
(syntax->datum #
