- Gambit-list - mailman.iro.umontreal.ca

changing the ld options on dynamically loaded files
by Bradley Lucier 29 Aoû '05

29 Aoû '05

Marc: I have the following code that used to work in an older beta of gambit: > (define-macro (setup-loader) > (set! ##ld-cmd "/usr/ccs/bin/ld -G %s.o libfftw.so.2.0.5 -o %s") > '(begin)) > > (setup-loader) > > (c-declare > " > #include \"fftw.h\" > > fftwnd_plan p; > > ") > > (define fftw2d_create_plan_backward > (c-lambda () > void > "p = fftw2d_create_plan(64, > 64, > FFTW_BACKWARD, > FFTW_ESTIMATE | FFTW_IN_PLACE); > ")) > > (define fftw2d_create_plan_forward > (c-lambda () > void > "p = fftw2d_create_plan(64, > 64, > FFTW_FORWARD, > FFTW_ESTIMATE | FFTW_IN_PLACE); > ")) > > ;;; Both forward and backward ffts, depends on which way the plan > was created. > > (define fftwc > (c-lambda (scheme-object) > void > " > int j; double *fp = (double *)((___WORD)___BODY_AS > (___arg1,___tSUBTYPED)); > fftwnd_one(p, > (fftw_complex *)(fp), > NULL); > for (j = 0; j < 64 * 64 * 2; j++) > fp[j] *= .015625; > ")) Now I get Gambit Version 4.0 beta 13 > (compile-file "all.scm") *** ERROR IN #<procedure #2> -- Unbound variable: ##ld-cmd and there's no ##ld-cmd in gambc40b14, either. How can I set things up to link all dynamically loaded files against libfftw.so.2.0.5? Brad

2 3

New chjmodule release, Perl interface
by Christian 29 Aoû '05

29 Aoû '05

Hello I've put up a new version of the chjmodule bundle, which now includes an alpha release of my gambit->perl interface. http://scheme.mine.nu/gambit/chjmodule/ Enjoy, and tell me if something doesn't work. Christian.

1 0

open-tcp-client problem?
by Francois Magnan 26 Aoû '05

26 Aoû '05

Hi, I have some difficulties using the open-tcp-client primitive on MacOSX 10.4 with Gambit-Cb14. The primitive returns a port before that port is actually ready to be used for sending/receiving data. See below for an example (Use two separate hosts to reproduce the error... don't try this with the client and server running on the same host). If the client (host B) is MacOSX 10.4 the second call to (do-call) fails. Any hints? Thank you, Francois Magnan ------------------- ;;; ;;;; -- ;;;; simple server ;;; ; Run this on host A (define (server-start) (let ((command-queue (open-tcp-server (list port-number: 5000 reuse-address: #t eol-encoding: 'cr)))) (let loop () (let ((incoming-connection (read command-queue))) (display "Got connection\n") (serve-command incoming-connection)) (loop)))) (define (serve-command incoming-connection) (let* ((parsed-command (read incoming-connection))) (display (list "received command" parsed-command)) (if parsed-command (write "toto" incoming-connection)) (close-port incoming-connection))) (thread-start! (make-thread (lambda () (server-start)))) ------------------- ;;; ;;;; -- ;;;; simple client ;;; ; run this on host B (define Host-A-IP "206.167.88.52") (define (do-call sleep?) (let* ((connection (open-tcp-client (list server-address: Host-A- IP ; put Host A IP here port-number: 5000 eol-encoding: 'cr)))) (if sleep? (thread-sleep! 1)) (write (list 1 2 3) connection) (display "\n" connection) (force-output connection) (let ((result (read connection))) (close-port connection) result))) (define (test) (thread-sleep! 1) (display "try with sleeping...\n") (do-call #t) (display "sleeping...\n") (force-output) (thread-sleep! 1) (display "now try without sleeping...\n") (do-call #f)) ;(##repl) (test) ; Fails on MacOSX 10.4 ; Works on Windows XP (MinGW) -------------------

3 3

clos-like system available?
by Kevin Smith 26 Aoû '05

26 Aoû '05

Googling has revealed naught, so I ask the enlightened inhabitants of this list: do any clos or clos-like implementations exist which work on Gambit 4? I'm playing with Meroon right now but it has a few issues just getting it to load into gsi. All the info I can find indicates that Meroon was ported to Gambit 3, but I was hoping it might work since it is the only lib I've been able to find. Thanks, Kevin

2 1

Specialize equal?, eqv?, and = to eq? when one of the arguments is a fixnum constant.
by Bradley Lucier 23 Aoû '05

23 Aoû '05

Marc: You should specialize equal?, eqv?, and = to eq? when one of the arguments is a fixnum constant. Brad

2 1

C++ defines in GUIDE
by Adam Langley 23 Aoû '05

23 Aoû '05

>From 4b14, lib/guide/guide.h: #define min(x,y) (((x)<(y))?(x):(y)) #define max(x,y) (((x)>(y))?(x):(y)) It's illegal to define max and min in this way in C++. Modern gcc's fail to compile this. With C++ std::min and std::max can be used. AGL -- 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

1 0

(declare (block)) and keyword arguments
by Bradley Lucier 20 Aoû '05

20 Aoû '05

Marc: I like keyword arguments, and would like to use them more, but they are relatively slow for small functions. So I have a question. Shouldn't it be possible with (declare (block)) to process keyword arguments at compile time rather than by calling ___GET_KEY at run time? Consider the following example: > (declare (block)) > > (define (foo #!key bar) > bar) > > (set! a (foo)) > > (set! b (foo bar: 2)) This expands to: > [lindv2:~] lucier% gsc -c -expansion test.scm > Expansion: > > (define foo (lambda (#!key (bar '#f)) bar)) > > (set! a ((lambda (#!key (bar '#f)) bar))) > > (set! b ((lambda (#!key (bar '#f)) bar) bar: 2)) and compiles to: > #undef ___PH_PROC > #define ___PH_PROC ___H__20_test > #undef ___PH_LBL0 > #define ___PH_LBL0 1 > #undef ___PD_ALL > #define ___PD_ALL ___D_FP ___D_R0 ___D_R1 ___D_R2 > #undef ___PR_ALL > #define ___PR_ALL ___R_FP ___R_R0 ___R_R1 ___R_R2 > #undef ___PW_ALL > #define ___PW_ALL ___W_FP ___W_R0 ___W_R1 ___W_R2 > ___BEGIN_P_COD > ___BEGIN_P_HLBL > ___DEF_P_HLBL_INTRO > ___DEF_P_HLBL(___L0__20_test) > ___DEF_P_HLBL(___L1__20_test) > ___DEF_P_HLBL(___L2__20_test) > ___DEF_P_HLBL(___L3__20_test) > ___DEF_P_HLBL(___L4__20_test) > ___DEF_P_HLBL(___L5__20_test) > ___END_P_HLBL > ___BEGIN_P_SW > ___DEF_SLBL(0,___L0__20_test) > ___IF_NARGS_EQ(0,___NOTHING) > ___WRONG_NARGS(0,0,0,0) > ___DEF_GLBL(___L__20_test) > ___SET_STK(1,___R0) > ___SET_R0(___LBL(2)) > ___ADJFP(4) > ___POLL(1) > ___DEF_SLBL(1,___L1__20_test) > ___SET_NARGS(0) ___GOTO(___L3__20_test) > ___DEF_SLBL(2,___L2__20_test) > ___SET_GLO(1,___G_a,___R1) > ___SET_R2(___FIX(2L)) > ___SET_R1(___KEY(0,___K_bar)) > ___SET_R0(___LBL(4)) > ___SET_NARGS(2) ___GOTO(___L3__20_test) > ___DEF_SLBL(3,___L3__20_test) > ___IF_NARGS_EQ(0,___SET_R1(___FAL)) > ___GET_KEY(3,0,0,1,___SUB(0)) > ___JUMPPRM(___NOTHING,___R0) > ___DEF_SLBL(4,___L4__20_test) > ___SET_GLO(2,___G_b,___R1) > ___SET_R1(___VOID) > ___POLL(5) > ___DEF_SLBL(5,___L5__20_test) > ___ADJFP(-4) > ___JUMPPRM(___NOTHING,___STK(1)) > ___END_P_SW > ___END_P_COD Couldn't it just be > Expansion: > > (define foo (lambda (#!key (bar '#f)) bar)) > > (set! a #f) > > (set! b 2) Brad

1 0

refcounts and threads
by Christian 20 Aoû '05

20 Aoû '05

Hello I've noticed that my perl interface leaked memory until I added a ___still_obj_refcount_dec call after allocation of a scheme object. This is in code which converts a perl datastructure to a scheme one; the resulting object is not used by C or perl code, only by scheme. So since a newly allocated still object starts with a refcount of 1, I have to decrement it again. I now do this immediately after allocation, e.g.: ___SCMOBJ /* for ___err */ gperl__SV_to_string_SCMOBJ (SV *sv, ___SCMOBJ* obj) { ... result = ___alloc_scmobj (___sSTRING, n<<___LCS, ___STILL); ___still_obj_refcount_dec(result); // now copy over perl string, then: *obj = result; return ___FIX(___NO_ERR); } I use the above from scheme like: (c-define-type SV* (pointer "SV" SV* "gperl_release_sv")) (c-define-type SV*->string "SV*" "SV_to_string_SCMOBJ" "NOTIMPLEMENTED" #f) (define sv->string (c-lambda (SV*) SV*->string "___result=___arg1;")) My question: is the above thread safe? Do I have to add (declare (not interrupts-enabled)), like: (define (sv->string sv) (declare (not interrupts-enabled)) ((c-lambda (SV*) SV*->string "___result=___arg1;") sv)) Thanks Christian.

1 1

macro troubles
by Alex Shinn 19 Aoû '05

19 Aoû '05

Gambit Version 4.0 beta 14 > (load "~~/syntax-case") "/usr/local/Gambit-C/syntax-case.scm" > (define-macro (foo . o) #f) *** ERROR -- invalid syntax (foo . o) Also, (include "macros.scm") will splice the forms in as the documents say, but only macros in that file will be available, and you'll get an error if they use any procedures defined in the same file. -- Alex

2 2

RE: [gambit-list] Newbie: define-macro question
by Logan, Patrick D 19 Aoû '05

19 Aoû '05

> 2. Making little sub-languages for specialized processing e.g. > > (with-vectors (v1 v2 v3) (v1 <- (+ v2 v3))) > > for summing up the vectors v2 and v3 and storing it in v1. Nice! I also liked the challenge in example #1 of allowing multiple bodies in the bindings. Here's a challenge for #2 -- would this language be any more usable by eliminating the need to declare the vectors, i.e. how about this... (with-vectors (v1 <- (+ v2 v3))) -Patrick

2 1