Hello fellow Schemers!
I have locally implemented and used srfi-4 (Homogeneous numeric vector
datatypes) and have attached a patch against git HEAD here.
All the different vector types of srfi-4 are subsumed in a new type
TC_INTVEC (which replaces the commented-out TC_COMBINATION_1 0x07, but
coul
> Fixed both bugs.
One more, make check now fails on one test:
;Run tests "runtime/test-dynamic-env"...
; Generating "test-dynamic-env.bin" because of: "test-dynamic-env.scm"
; Generating SCode for file: "test-dynamic-env.scm" =>
"test-dynamic-env.bin"... done
; Generating "test-dynamic-env.c
Hello Chris!
One more, commit 69e6107c introduced optional parameters #!optional
start to vector-fill!, but end was overlooked (even though used in the
function).
I'd suggest the following:
diff --git a/src/runtime/vector.scm b/src/runtime/vector.scm
index 75baafb..90b4319 100644
--- a/src/runtim
Hello Chris!
Just a short notice, commit 70220c78a1ebd64ca276b831892e9315b7f08e7b
(Fix parameterization in unpars.scm.) has the following:
- (list (cons *unparse-with-maximum-readability?* #t))
+ (list (cons param: #t))
which to me seems like it is missing
> Fixed in commit aed45b8. Sorry, I missed a hunk of your 2012 patch.
Thanks, as no-one hit this problem until now, not a big problem :)
Thanks for fixing it!
> ~/.scheme.init fluid-let a variable that is now a fluid object?
Sorry, right after sending the mail I noticed .scheme.init there, and
Greetings!
I've again been playing around with the FFI, and found that struct
parameters seem to work beautifully, however struct return values suffer
from the following problem.
Given the following cdecl:
(typedef TCOD_color_t (struct (r uchar) (g uchar) (b uchar)))
(extern TCOD_color_t
Hello!
I've been playing around with displaying images in the Emacs SLIME REPL
from MIT/GNU Scheme, works very nicely so far. Now I've tried to get a
halfway decent binding for cairo (http://cairographics.org) working, but
run into a problem:
There is a function
cairo_status_t [an int]
cairo_sur
> 0244 is an ISO-8859-1 (nee Latin-1, nee ASCII) "generic currency sign"
> -- a graphical character. 0237 is undefined, non-graphical,
> slashified.
>
> https://en.wikipedia.org/wiki/ISO/IEC_8859-1
>
> So I think we're OK.
Is there a way to globally (or for a port) tell MIT/GNU Scheme to neve
I forgot to mention this in the email just now:
> (wide-string->utf8-string (utf8-string->wide-string "ÄÖüäößſ"))
"�\204�\226üäö�\237ſ"
The problem *seems* to be that the second byte of each utf-8 sequence is
*not* actually output as the octal character \204, but instead the
characters "\204" (wh
Hello fellow Schemers!
I've run into a curious problem. I'm working with UTF-8 files. Generally
things work very well, however (on a UTF-8 terminal):
1 ]=> "ä"
;Value 13: "ä"
1 ]=> "ß"
;Value 14: "Ã\237"
1 ]=> "\303\244"
;Value 15: "ä"
1 ]=> "\303\237"
;Value 16: "Ã\237"
Why does ä (\303\
Hello fellow Schemers!
I'm playing around with OpenGL bindings in MIT/GNU Scheme. I'm using
GLFW as the toolkit to access window-related functions. It includes a
function glfwSetKeyCallback, which is supposed to set a callback
function that is called whenever a key is pressed or released.
It does
Hello MIT/GNU Schemers!
I've been looking for UDP support, but found that - while the actual
functions would be the same - the microcode implements only TCP. Is
there any reason *not* to change the microcode primitives so that they
get two additional parameters (the domain and the type, see "man 2
On Wed, 2 May 2012 22:44:44 -0700, Chris Hanson wrote:
> You're confused because URL:ENCODE-STRING has nothing to do with "url
> encoding", which the encoding used for
> application/x-www-form-urlencoded (and which itself has nothing to do
> with URIs).
>
> As the code comment says, this is just
Hello fellow Schemers!
I may misunderstand things here, but isn't URL:ENCODE-STRING meant to
propertly encode characters that are special to urls? Examples would be
=, & and ; (which should all be encoded). However,
> (url:encode-string "a=b&b=c;c=d")
just echoes that string literally ("a=b&b=
Found another typo in the description of signal-condition.
Greetings,
Peter
From 61bb14a32a8183645b73eefdbe90da32966ac64a Mon Sep 17 00:00:00 2001
From: Peter Feigl
Date: Wed, 2 May 2012 09:30:36 +0200
Subject: [PATCH] fixing typo: duplicated word "creates"
---
doc/ref-manual/error.texi |2
Hello fellow Schemers!
Yesterday I've tried to get current SLIME (2012-03-06 here) to work with
MIT/GNU Scheme, and fixed a few things. Find attached my patches. How
should I best prepare them so they get a chance at getting accepted into
GIT?
Greetings,
Peter
From 203f5ab2624f366b41b0dcd144f1fa
Hello fellow Schemers!
Another question, what is an efficient way to read from a network (or
unix domain) socket? After reading the manual, I'd guess READ-SUBSTRING!
with an aptly allocated string and then using VECTOR-8B-REF etc. to
access the actual values. Is this correct? Is there any further
Hello Schemers!
I just happened across the following exchange:
1 ]=> false?
;Value 13: #[compiled-procedure 13 ("boole" #x1) #x14 #xb2d8f4]
I've been wondering oftentimes why compiled procedures only show an
index and a "package" and *not* their actual name. Is there a real
reason for this? It
A quick fix for a typo I found while reading the manual. I'm not sure
about how to best send in patches, is e-mailing them to the list ok?
Greetings,
Peter
---
doc/ref-manual/lists.texi |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ref-manual/lists.texi b/doc/ref-man
Hello fellow Schemers!
I'm trying to get information from a condition, to present to the
user. I've already found WRITE-CONDITION-REPORT, which prints a
message. I'd like to show a stack trace as well as file and line number
information, if possible. I've found that debug.scm uses
dstat/expression
Hello fellow Schemers!
I've been playing around with multiple threads in GNU/MIT-Scheme. I've
tried the following code:
(let ((socket (open-tcp-server-socket 54321)))
(create-thread #f (lambda ()
(let ((sock (tcp-server-connection-accept socket #t #f)))
21 matches
Mail list logo
