-
Hi,
I am just playing/exploring, but I love this library!
A question came up when I was trying to do a minimal [hello world example](https://github.com/bstpierre/gtk-examples/blob/98aa5ebe6f850e5…
-
For portability-testing a feature across many implementations, it would be great if we could do something like this:
`docker run schemers/bigloo scheme-eval "(+ 1 (* 2 3))"`
It would evaluate th…
-
@diamond-lizard I'm opening this issue to explore the SRFI metadata problem specifically, since the scope of [pre-srfi/scheme-metadata-files](https://github.com/pre-srfi/scheme-metadata-files) is both…
-
Currently, splicing let-syntax is kind of equivalent to define-syntax in that the following is valid:
(let ()
(let-syntax ([foo (identifier-syntax 12)])
(define-syntax x (identifier-syntax foo)…
hyln9 updated
10 years ago
-
> The behavior on overlow is not specified. This allows compliant Scheme implementations to exist with de-facto C number semantics.
This seems problematic. C is allowed to crash on overflow. Is Sch…
-
Cell(0 0) in the table would be better like SRFI/Implementation platform.
-
-
```
What steps will reproduce the problem?
1. evaluate (expt +inf.0+2.0i 2)
What is the expected output? What do you see instead?
It should be: +inf.0++nan.0i. It is: +inf.0++inf.0i.
What version of…
-
We will have a large number of automated builds on Docker Hub, because I think we will want to keep using Docker's public build infrastructure. Using their infrastructure is some kind of guarantee tha…
-
It would be very useful if Chez Scheme could show line numbers associated with errors (for example, if a variable is referenced but is undefined, outputting the line the use was on, or showing the lin…