Gambit-list Juin 2008

gambit-list@iro.umontreal.ca

23 participants
19 discussions

Edge triggered I/O with libevent
by Adam Langley 04 Avr '13

04 Avr '13

Gambit uses the select call on POSIX systems to multiplex IO operations. This is fine for small numbers of file descriptors, but falls apart quickly with large numbers[1]. libevent[2] is a wrapper library around a number of modern IO multiplexing systems (epoll on Linux, kqueue on the BSDs as well as poll and select). Attached is a patch which converts Gambit to using edge triggered I/O with epoll and libevent. This also requires a patch (attached) of libevent since the standard distribution doesn't include edge triggering support and the upstream appears to be on holiday. (epoll is required because I don't have a BSD box on which to develop edge triggering support for kqueue) This patch (for Gambit) preprocesses away to nothing unless --enable-libevent is passed to the configure script. (Note that, since this patches the configure.ac script, you'll need to run autoconf to regenerate). I hope I've not broken anything, but at this stage I've only tested that the console and tcp ports work. This patch (in the future) should also allow people, who write programs which use socket calls directly, to integrate into the main event loop at some point. Testing is more than welcome and, if you find a form of IO which is broken, please email me. [1] http://monkey.org/~provos/libevent/libevent-benchmark2.jpg [2] http://monkey.org/~provos/libevent/ -- Adam Langley agl(a)imperialviolet.org http://www.imperialviolet.org (+44) (0)7906 332512 PGP: 9113 256A CC0F 71A6 4C84 5087 CDA5 52DF 2CB6 3D60

2 2

Space Invaders on gambit-c
by David St-Hilaire 21 Aoû '08

21 Aoû '08

Hi all! I just wanted to let you know that I've just put my space invaders (the classic arcade game) re-make on the dumping grounds. There are also pre-compiled binaries available on my web page (http://www-etud.iro.umontreal.ca/~sthilaid/). The game runs over glut and SDL and should be compatible at least with linux, windows and mac systems (execpt that the glut user interface does not seem to work in windows...). Compilation insights is provided in the README file. Just send me a mail for help, question, comments, or most likely, bug reports! ;) Enjoy! ^_^Y David

2 1

Illegal character
by adamsonj＠email.unc.edu 02 Jul '08

02 Jul '08

Hello Gambit-List, I have compiled a dynamically-loadable library as per the Gambit Manual, and when I try to load it: ,----Error! | > (load "genxic.o") | *** ERROR IN "genxic.o"@1.5 -- Illegal character: #\x01 | 1> `---- I have tried all sorts of things, and it doesn't seem to depend on the options I use or which files I"m compiling. Where should I turn next? Any suggestions? Joel -- Joel J. Adamson (303) 880-3109 Public key: http://pgp.mit.edu http://www.unc.edu/~adamsonj http://trashbird1240.blogspot.com

3 10

Archives of the #gambit irc channel?
by Bradley Lucier 01 Jul '08

01 Jul '08

I'm not really an IRC person (maybe I'm too old, maybe it's my day job), but I was wondering if there are logs of the #gambit IRC channel like the http://tunes.org/~nef/logs/scheme/08.06.27 logs for the #scheme IRC channel. Brad

5 5

Patching gambit to fix out of source build
by Nathan Thern 29 Jui '08

29 Jui '08

Hello Gambit developers- I have successfully built, packaged and installed gambit on cygwin. The build system I used - cygport - defaults to an out-of-source build, which is supported by gambit's configure (or so it claims). It very quickly became apparent that out-of-source builds are broken, but I stubbornly patched the makefiles until it worked. What I've got now is a bit kludged, but should be fairly simple to maintain as long as the future gambit build system doesn't change drastically. However, having come this far... I would be willing to further my work on patching configure.ac and the makefile.in's so gambit supports out-of-source builds and DESTDIR style installs. I can test on cygwin, RHEL, debian and solaris. I figure I'm about 1/3rd of the way there and I don't want to chew up any more of my time unless you are interested in accepting patches. Are you? regards, Nate T BTW, I haven't installed mercurial yet, so I haven't looked at the source repository, only the v4.2.8 release source.

5 10

Undefined symbol in c-lambda
by adamsonj＠email.unc.edu 25 Jui '08

25 Jui '08

Dear Gambit-List, I have the following problem: I have a C header file that I use to include all the C files I need, and define a single function that transfers between C vectors and Scheme f64vectors. I have included this file in my "Scheme header" so I can compile a single file. Incidentally, I also include the C header (gsl_genx.h) in each Scheme module. Compilation with gsc goes just fine, but when I load the file with gsi, I get an error. Here are the files and the error: ************************************************** /home/joel/lisp/scm/genxic/gsl_genx> cat gsl_genx.h /* -*- mode:c -*- */ /* $Id$ */ /* */ /* gsl_genx.c */ #ifndef ___GSL_GENX #define ___GSL_GENX #include <stdio.h> #include <stdlib.h> #include <stdbool.h> #include <gsl/gsl_vector.h> #include <gsl/gsl_matrix.h> #include <gsl/gsl_blas.h> #include <gsl/gsl_errno.h> /* C function for transferring vectors */ /* this could be better defined as a function-like macro */ int f64vector_length (___SCMOBJ); double f64vector_ref (___SCMOBJ, int); double * scm_vector_to_C (___SCMOBJ f64vec) { /* initialize the length of the vector */ int len = f64vector_length (f64vec); /* initializes the new vector */ double * newCvec = malloc (len*sizeof (double)); /* declare a counter */ int i; /* iterate over the length of the vector copying each object into the new vector */ for (i = 0; i<len; i++) { /* could be re-written using pointer arithmetic */ newCvec[i] = f64vector_ref (f64vec, i); } return newCvec; } #endif /home/joel/lisp/scm/genxic/gsl_genx> cat gsl_genx.scm ;; -*- mode:scheme -*- ;;$Id$ ;; ;; gsl_genx.scm ;; header file for GSL API (c-declare "#include \"gsl_genx.h\"") (include "gsl_structures.scm") (include "gsl_lalgebra.scm") (include "gsl_wrapper.scm") ;; end of gsl_genx.scm /home/joel/lisp/scm/genxic/gsl_genx> gsc gsl_genx.scm /home/joel/lisp/scm/genxic/gsl_genx> gsi gsl_genx *** ERROR IN ##main -- /home/joel/lisp/scm/genxic/gsl_genx/gsl_genx.o11: undefined symbol: gsl_matrix_get_row (load "gsl_genx") /home/joel/lisp/scm/genxic/gsl_genx> ************************************************** And the function with gsl_matrix_get_row (in gsl_structures.scm): ************************************************** (define gsl-row-vector ;; gets the row of matrix and sets it equal to a vector (c-lambda (gsl-vector* gsl-matrix* int) gsl-vector* "gsl_matrix_get_row (___arg1, ___arg2, ___arg3); ___result_voidstar = ___arg1;")) ************************************************** Now, the obvious problem is that the symbol *is* defined in gsl/gsl_matrix.h. If I comment the function that uses gsl_matrix_get_row, then the next one comes up with the same error. I've looked at the resulting C file (gsc -c gsl_genx.scm), and gsl_genx.h is included. What am I missing here? An added note: i used a different (less logical) organizational scheme before, and I didn't have this problem. I will again humbly point out that I know a lot more about Scheme than I know about C ;) Thanks, Joel -- Joel J. Adamson (303) 880-3109 Public key: http://pgp.mit.edu http://www.unc.edu/~adamsonj http://trashbird1240.blogspot.com

2 2

printf and the C interface
by Cristian Baboi 20 Jui '08

20 Jui '08

Hello! This is my first try to use the C interface of gambit-c. I used gambit-c 4.2.8 and mingw gcc compiler from CodeBlocks under Windows XP. Running alt.exe, I get: Hello World! from C begin 137end The lines printed from the C function appear before the lines printed by scheme. I have two questions: 1) Why the output lines do not appear in the call order ? 2) Is this the correct way to get small executables with gambit-c or it can be done in a better way ? Thank you! functii.c ---------- #include <string.h> #include <stdio.h> int hello(char * s){ printf("%s",s); return strlen(s); } test.scm ---------- (c-declare #<<c-declare-end extern int hello(char *s); c-declare-end ) (c-define-type MyInt int) (c-define-type MyString char-string) (define myHello (c-lambda (MyString) MyInt "hello" )) alt.scm --------- (display "begin") (newline) (display (myHello "Hello World!\n")) (display (myHello "from C\n")) (display "end") (newline) compile.cmd ------------ @echo off set PATH=E:\limbaje\CodeBlocks\MinGW\bin;%PATH% gsc -link -o leg.c test.scm gcc -shared -mwin32 -m32 -march=pentium4 -IE:\limbaje\gambit-gcc\v4.2.8\include -IE:\limbaje\CodeBlocks\MinGW\include -LE:\limbaje\gambit-gcc\v4.2.8\lib -LE:\limbaje\CodeBlocks\MinGW\lib -o test.dll -Wl,--output-def,test.def -Wl,--kill-at -Wl,--out-implib,test.a -Wl,-s -D___SINGLE_HOST -D___LIBRARY -D___SHARED test.c leg.c functii.c -lgambc -lws2_32 gsc -link -l leg -o lleg.c alt.scm gcc -mwin32 -m32 -march=pentium4 -IE:\limbaje\gambit-gcc\v4.2.8\include -IE:\limbaje\CodeBlocks\MinGW\include -LE:\limbaje\gambit-gcc\v4.2.8\lib -LE:\limbaje\CodeBlocks\MinGW\lib -D___SINGLE_HOST -D___SHARED -Wl,-s -Wl,--enable-auto-import alt.c lleg.c test.a -o alt.exe set PATH=%PATH:E:\limbaje\CodeBlocks\MinGW\bin;=% gcc -v ======== Reading specs from E:/limbaje/CodeBlocks/MinGW/bin/../lib/gcc/mingw32/3.4.5/specs Configured with: ../gcc-3.4.5/configure --with-gcc --with-gnu-ld --with-gnu-as - -host=mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls -- enable-languages=c,c++,f77,ada,objc,java --disable-win32-registry --disable-shar ed --enable-sjlj-exceptions --enable-libgcj --disable-java-awt --without-x --ena ble-java-gc=boehm --disable-libgcj-debug --enable-interpreter --enable-hash-sync hronization --enable-libstdcxx-debug Thread model: win32 gcc version 3.4.5 (mingw-vista special) ________ Information from NOD32 ________ This message was checked by NOD32 Antivirus System for Linux Mail Servers. part000.txt - is OK http://www.eset.com

4 7

Re: [gambit-list] call/cc behavior in gambit-c vs. plt-scheme
by Nicholas Walton 17 Jui '08

17 Jui '08

Christian, You're quite correct. It would appear that the final act in the continuation is to load the file. Hence the recursive loop. Can't say why though. Maybe a bug perhaps? Nick Walton On 11 Jun 2008, at 10:56, Cristian Baboi wrote: > On Wed, 11 Jun 2008 12:50:36 +0300, Nicholas Walton > <nwalton(a)mac.com> wrote: > >> I think you've had finger slip somewhere, when I ran the example >> the results where as expected > > I don't know what is expected. > If you run the whole file from gambit-c, you'll get what I wrote. > If you omit the last line from the file and enter it at the prompt, > you don't get the loop. > However, the question was about the different results in plt-scheme > and gambit-c. I don't know which one is wrong. > >> Gambit v4.2.2 >> >> > (define (call/ccc x) (call-with-current-continuation x)) >> > >> (define coco 1) >> > >> (begin >> (display "begin") (newline) >> (call/ccc (lambda (c) (set! coco c))) >> (display "again") (newline) >> (display "end") (newline) >> ) >> begin >> again >> end >> > >> (coco 13) >> again >> end >> > >> >> Nick Walton >> > > > ________ Information from NOD32 ________ > This message was checked by NOD32 Antivirus System for Linux Mail > Servers. > part000.txt - is OK > http://www.eset.com

4 4

call/cc behavior in gambit-c vs. plt-scheme
by Cristian Baboi 11 Jui '08

11 Jui '08

Hello! Trying to learn scheme, I've made this small test file and tried it in gambit-c and plt-scheme. (define (call/ccc x) (call-with-current-continuation x)) (define coco 1) (begin (display "begin") (newline) (call/ccc (lambda (c) (set! coco c))) (display "again") (newline) (display "end") (newline) ) (coco 13) The result was: - plt-scheme printed: begin again end 13 - gambit-c printed: begin again end again end again end ... My question: which one is the intended behavior ? Thank you! ________ Information from NOD32 ________ This message was checked by NOD32 Antivirus System for Linux Mail Servers. part000.txt - is OK http://www.eset.com

4 5

SDL-proto updated
by Ken Dickey 06 Jui '08

06 Jui '08

I have added another bit of SDL [Simple Direct-media Layer] code to SDL-proto in the dumping grounds. In addition to TinyTalk, I have added an example using Oops! to contrast a more CLOS-ish style and made the test build/compile process easier. Please ignore the many compiler/loader warnings. Test 1 -- From a SDL Tutorial [ http://www.libsdl.org ] Test 2 -- Drag a rectangle around in a window Test 3 -- A drag test using TinyTalk object system Mouse targeting and event dispatch Bitmapped background Separate render and event threads Test 4 -- Like Test 3, but using the Oops! object system In each case, use the same strategy to build and run, but use the test-number you want [Linux]: [1] >> ./compile-test1 ## test2 test3 test4 [2] >> gsi [3] > (load "test1") (run-test) ;; "test2" "test3" "test4" [4] > (exit) Note the separation: - SDL interface code is in "sdl-interface.scm" - SDL independent OO graphic definitions are in "sdl-tt.scm" and "sdl-oops.scm" - Test code which puts the two together and has run-test and stop-test functions are in files "test2.scm", "test3.scm" and "test4.scm". Code for both object systems is included. I have tested only under Linux. Please send fixes/suggestions. Cheers, -KenD

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Gambit-list Juin 2008