using GSL with cblas via FFI

Hi, I'm trying to use GSL through the FFI, but the program is not linked to libgslcblas, so it cannot find some functions. Attached a minimal example. Cheers, Johan (use-modules (system foreign) (rnrs bytevectors)) (define libgsl (dynamic-link "libgsl")) (define libgslcblas (dynamic-link "

Re: using GSL with cblas via FFI

defined symbol: cblas_dtrsv === 2011/3/25 Ludovic Courtès : > Hi Johan, > > Johan Hidding writes: > >> I'm trying to use GSL through the FFI, but the program is not linked >> to libgslcblas, so it cannot find some functions. Attached a minimal > > Can you please post yo

sample guile-2.0 extension in manual

Hi, In manual chapter 5.3.1 there is a small example program. Using GCC 4.6, this only compiles with -fpermissive, unless an explicit reinterpret_cast (which is an alias for (void *)) is used. Should this be considered a (minor) bug in the manual? Cheers, Johan

Re: Reader syntax for accessing arrays

Hi Maciej, I've been thinking among the same lines. At the same time this syntax could be used to access members of a 'struct' or 'class' object. It should be relatively simple to write a small interpreter (or maybe a pre-compiler). Otherwise you could make a wrapper around the array in the form of

Re: Reader syntax for accessing arrays

Hi, I think it is a question of philosophy. The suggested [] syntax contains the scent of both infix notation (would [7 '* 6] work?) and work on arrays in stead of lists (also in the case of object member reference; the most straight forward implementation would be having a memory offset assigned t

array vs. bytevector

Hi, I was playing around with guile arrays, saving and restoring them from disk. There are nice method called (uniform-array-read! ...) and (uniform-array-write ...), however these are depricated in favour of bytevector i/o. What is the prefered method to interpret the data as an array? There is (b

Re: array vs. bytevector

Hi, I think I found the answer in that I should use (array-contents ...) as such: (import (rnrs io ports)) (put-bytevector (%make-void-port "w") (array-contents #2f64((1 2) (3 4 Cheers, Johan 2011/9/15 Ludovic Courtès : > Hi, > > Johan Hidding skribis: > >>

getting pipes going

Hi everyone, I'm having difficulties getting (open-pipe ...) to work for me. I would expect the following code: (use-modules (ice-9 popen)) (display (with-output-to-string (lambda () (let ((P (open-pipe "cat" OPEN_WRITE))) (display "Hello World!\n" P) (close-p