guile-cairo 1.11.1 released

ns as well. This release builds on freebsd (i386, armv7, and amd64). Thanks to RhodiumToad on #guile for the fix and the testing. Regards Daniel Llorens Grab the archive for this release from http://download.savannah.gnu.org/releases/guile-cairo/guile-cairo-1.11.1.tar.gz

guile-cairo 1.11.0 released

d any bugs in the software, the documentation, or the website, please report them to guile-user@gnu.org. Regards Daniel Llorens Grab the archive for this release from http://download.savannah.gnu.org/releases/guile-cairo/guile-cairo-1.11.0.tar.gz http://download.savannah.gn

Re: guile-user Digest, Vol 194, Issue 29

> On 28 Jan 2019, at 18:00, guile-user-requ...@gnu.org wrote: > From: Matt Wette > Subject: Re: Matrix or array operations library > Date: 27 January 2019 at 19:41:57 CET > To: guile-user@gnu.org > … > Also, is it possible to get a pointer to the first element of a

Re: Function set-gl-vertex-array in Guile-opengl

> On 26 Jan 2019, at 17:05, Luis Souto Graña wrote: > > The structure of my byvector is: > > 30.0(float) --- IEE754 converter --> 0x41F0 (hexadecimal) --- little > endian ---> F041 --- hexadecimal to decimal converter ---> 00 00 240 65 > > But I didn't notice and there's a lot of z

Re: Function set-gl-vertex-array in Guile-opengl

> On 26 Jan 2019, at 13:52, Daniel Llorens wrote: > > > >> On 26 Jan 2019, at 02:33, Luis Souto Graña wrote: > > >>>> >>>> ,apropos set-gl-vertex-array >>> (gl): set-gl-vertex-array#>> bv-or-pointer #:optional

Re: Function set-gl-vertex-array in Guile-opengl

float addresses. It's unnecessary and error prone to use the bytevector functions to handle typed vectors unless you really need to address the bytes. Don't define your own f32vector. Use SRFI-4. Regards Daniel > > If anyone could make an minimal example with

Re: Function set-gl-vertex-array in Guile-opengl

Hi Luis, I don't really have an answer to your question, but I wanted to point out that Guile already has make-f32vector, f32vector-set!, etc. You don't need to define your own. IMO it's not a good idea to use bytevector-xxx-set!/ref to operate on typed vectors unless you are type punning.

Re: guile-user Digest, Vol 193, Issue 35

> From: Matt Wette > Subject: Re: Matrix or array operations library > Date: 29 December 2018 at 00:24:38 CET > To: guile-user@gnu.org > > > On 12/28/18 12:23 PM, Daniel Llorens wrote: >> >> John already wrote a nice explanation of how array strides work. Yo

Re: Matrix or array operations library

> On 29 Dec 2018, at 00:16, John Cowan wrote: > If array objects don't have an offset (the index in the backing store of the > [0,0, ... 0] element), you can't do arbitrary translations, unfortunately. > If Guile doesn't have that, it should. It does; I just forgot to mention it. make-shar

Re: Matrix or array operations library

> From: Matt Wette > Subject: Re: Matrix or array operations library > Date: 27 December 2018 at 23:24:51 CET > To: guile-user@gnu.org > > On 12/27/18 10:43 AM, Daniel Llorens wrote: >> 1) Guile already has a multidimensional array type with strides and all >>

Re: Matrix or array operations library

>> With regard to NumPy, especially the stuff about the "strides" (whatever >> that is) in the data buffer of a NumPy array and how what changes when >> creating a view and changing indices (For example I cannot imagine a >> single reason, why the ordering of how one writes the indices would >> m

Re: need help for new guile-cairo release

> Just a minor note. It would be nice to mention somewhere in the > repo docs that guile-lib is necessary for `make check' to work. Thanks Vladimir, we'll add a note to the README and also to the website. Please let us know if you notice anything else! Regards Daniel signature.asc

guile-cairo 1.10.0 released

o Please report any errors in the documentation as well. The documentation generation system is broken at the moment and it's possible that the documentation has become outdated in places. However I didn't want that to hold a release that is much overdue. Regards Daniel Llore

need help for new guile-cairo release

Hi Guilers, Cairo (https://cairographics.org/) is a popular, high level 2D drawing library. Andy Wingo wrote Guile bindings for it: guile-cairo. Cairo lets you draw directly to a bitmap, to SVG, to PDF, etc. and the Guile bindings cover most of the library. The only real competition might be

Re: test-out-of-memory fails in v2.2.2?

With gcc-7.2.0 and gcc-6.4.0, both built from source (just guile/configure ... CC=gcc-X.X). - stable-2.2 with 6.4 passes the tests every time. - stable 2.2 with 7.2 fails on test-out-of-memory. Running make check repeatedly I got F F F P F F P P P P F F F F P. regards Daniel

Re: test-out-of-memory fails in v2.2.2?

fwiw, I've been seeing this for months. The test passes sometimes, it seems to be random. regards Daniel > From: Dan Kegel > Subject: test-out-of-memory fails in v2.2.2? > Date: 26 Nov 2017 06:10:08 GMT+1 > To: guile-user@gnu.org > > > Hi! Just trying to build scheme here. > > sch

raw string literal reader extension

Hi, https://github.com/lloda/guile-raw-strings is a reader extension to be able to write string literals verbatim, without escapes. E.g. you can write #R-(quotes " and escapes \ and newlines can " freely be used " here)- where you'd normally need escapes: "quotes \" and escapes \

Re: GNU Guile 2.1.7 released (beta)

On 28 Feb 2017, at 01:04, David Pirotte wrote: > Hi Andy, > >> So! Release blockers. >> ... > > Not a blocker, at all, but I was thinking to this, wrt manipulating (very) > large > vectors, arrays, lists ... > > -]repl - truncated-print > > Right now I edit the installed (system repl c

running Ao (was Re: bug-guile Digest, Vol 167, Issue 7)

On 18 Feb 2017, at 18:00, bug-guile-requ...@gnu.org wrote: > From: P Dii > Subject: bug#25780: version number > Date: 18 Feb 2017 03:44:25 GMT+1 > To: 25...@debbugs.gnu.org > > Hi, > > I am having a few problems with guile, I am not sure if this is the right > place but the mailing list "htt

Re: name an array function

On 23 Nov 2016, at 21:48, David Pirotte wrote: > Le Wed, 23 Nov 2016 17:07:30 +0100, > Daniel Llorens a écrit : > >> On 21 Nov 2016, at 14:56, to...@tuxteam.de wrote: >> >>> I (politely) disagree: the most "commonly" used function is >>> a

Re: name an array function

On 21 Nov 2016, at 14:56, to...@tuxteam.de wrote: > I (politely) disagree: the most "commonly" used function is > already array-ref, so you would seldomly use array-from/slice > for a scalar result (the rank-0 result will be more frequent, > because there's no substitute). But hey, as I said. I

Re: name an array function

On 21 Nov 2016, at 15:01, Panicz Maciej Godek wrote: > As far as accessors are concerned, I'm not sure whether they actaully need > names. Maybe it would be better to make them applicable, and produce > "procedures with setters"? I'd absolutely prefer (A i j) to (array-whatever A i j). Arrays

Re: name an array function

On 21 Nov 2016, at 14:24, to...@tuxteam.de wrote: > So should "slice" prevail, it'd make sense to "invert" the star > (array-slice corresponding to array-from* and vice-versa)? I think it's more important to give the simpler names to the functions that are more commonly used. So I would keep th

Re: name an array function

On 21 Nov 2016, at 13:55, wrote: > > it (numpy, to mention a popular one. You don't need to say A[i, :, :], > > you can just say A[i].). However, the maintainers spoke against this, > > so these functions need different names. > > Understandable... but a pity, really. yeah... > Uh, oh. That'

name an array function

Hello, version 2.2 of Guile will (I hope) include rank-polymorphic versions of array-ref, array-set! and array-for-each. What this means is that instead of requiring as many indices as the rank of the array, with these functions you can give fewer indices and get a subarray (a ‘prefix slice’).

Re: Goops generic-functions and srfi-64 tests

On 23 Nov 2014, at 14:47, Taylan Ulrich Bayırlı/Kammer wrote: > Daniel Llorens writes: > >> SRFI-64 has all these specific binary predicates: test-eqv, >> test-equal, test-eq, test-approximate, but no way to pass your own >> predicate, which is annoying. Please

Re: Goops generic-functions and srfi-64 tests

On 22 Nov 2014, at 18:00, guile-user-requ...@gnu.org wrote: > Why it happens, is clear. Since scheme macros are hygienic, equal? in > expansion of `assert-equal` is sealed to refer to (@@ (srfi srfi-64) > equal?). I belive, in presence of goops, it would be nice add > > (define-syntax equa

[ANN] guile-ffi-cblas

Hello, this is to announce that I've started a BLAS (Basic Linear Algebra Subprograms) wrapper for Guile using the FFI. The wrapper is actually for CBLAS, not that there's much difference. https://gitorious.org/guile-ffi-cblas Currently the wrapper covers: dot, axpy, nrm2, scal, asum, iamax,

Re: FFI bindings for FFTW

On Feb 26, 2014, at 18:00, guile-user-requ...@gnu.org wrote: > Date: Tue, 25 Feb 2014 17:10:31 + > From: Neil Jerram > To: guile-user@gnu.org > Subject: Re: FFI bindings for FFTW [...] >> This is my first time using the FFI. There are some portability issues >> such as the lack of library

FFI bindings for FFTW

Hello, I've written a minimal wrapper for FFTW (http://www.fftw.org/fftw3_doc/Guru-Interface.html#Guru-Interface). https://gitorious.org/guile-ffi-fftw It provides two functions, (fftw-dft! rank sign in out) and (fftw-dft rank sign in). --- There is another set of bindings by Mikael

Re: How to read integers from file faster?

> Date: Sun, 01 Sep 2013 22:55:56 +0200 > From: "Pascal J. Bourguignon" > To: guile-user@gnu.org > > Darren Hoo writes: > >> It is way too slow to read numbers from a file simply by using `read' >> >> for example a txt file contains 10,000,000 line of numbers: > > To get speed, I would: >

Re: (help) vs ,describe

On Jan 22, 2013, at 10:26, Andy Wingo wrote: > The reason is the use of apropos-fold-exported in (ice-9 session)'s > `help-doc'. > > Want to propose a patch that makes more sense, including private > bindings from the current module? Thanks for the pointer, I'll look into it. Regards,

(help) vs ,describe

(help) doesn't seem to work for procedures defined in the REPL. scheme@(guile-user)> (define (hello x) "hello for x" x) scheme@(guile-user)> (procedure-properties hello) $1 = ((arity 1 0 #f) (name . hello) (documentation . "hello for x")) scheme@(guile-user)> ,describe hello hello for x scheme

Re: case-lambda* question

On Jan 14, 2013, at 11:39, Andy Wingo wrote: … > The attached patch fixes the problem. If there are no comments against > it, I will apply it to stable-2.0. It does introduce a slight > incompatibility, but I don't think there are many case-lambda* users, > and it makes cases work that previou

Re: repl, abridged output?

On Dec 4, 2012, at 02:43, Daniel Hartwig wrote: > On 3 December 2012 20:39, Daniel Llorens wrote: >> I've seen that there's a REPL command ,inspect that produces >> abridged output. Is it possible to have this as the default for >> printing to the REPL? Is

repl, abridged output?

Hello, When I work with large arrays or other large data structures on the command line, I have to be careful not to print them. Guile always prints these things in full, it takes forever and often I can't even C-c. I've seen that there's a REPL command ,inspect that produces abridged

Re: case-lambda* question

On Nov 15, 2012, at 02:22, Daniel Hartwig wrote: > On 14 November 2012 18:20, Daniel Llorens wrote: >>> When the doc. states keyword arguments do not contribute to the >>> success of a match, it refers only to keyword arguments in the >>> case-lambda clause, not

Re: case-lambda* question

On Nov 13, 2012, at 03:46, Daniel Hartwig wrote: > On 12 November 2012 21:54, Daniel Llorens wrote: >> >> (define f >>(case-lambda* >>((a b c #:key x) 3) >>((a #:key x) 1))) >> >> scheme@(guile-user)> (

case-lambda* question

(define f (case-lambda* ((a b c #:key x) 3) ((a #:key x) 1))) scheme@(guile-user)> (g 0 #:x 1) $1 = 3 The manual says > Also, for completeness. Guile defines case-lambda* as well, which is like > case-lambda, except with lambda* clauses. A case-lambda* c

Re: A mess with GOOPS

On Jan 10, 2012, at 13:22, Daniel Llorens wrote: > On Jan 9, 2012, at 18:11, Andy Wingo wrote: > >> Ew. Why don't we instead allocate a typecode for arrays. I just pushed >> a patch to do that, and for bitvectors as well. Copying Daniel Llorens, >> to che

Re: A mess with GOOPS

On Jan 9, 2012, at 18:11, Andy Wingo wrote: > Ew. Why don't we instead allocate a typecode for arrays. I just pushed > a patch to do that, and for bitvectors as well. Copying Daniel Llorens, > to check that I didn't break arrays. I've just tested g3248c95 and I

Re: A mess with GOOPS

>> While compiling expression: >> ERROR: In procedure vector-length: Wrong type argument in position 1 >> > > Oh, and I forgot to mention -- the error appears when I try > to apply these funtions to regular (non-typed) array with rank > 1. > It works for typed arrays, vectors and uvecs. > > I'l

Re: the future of guile

On 4 Dec, 2007, at 18:01, [EMAIL PROTECTED] wrote: 1a. Why functions like SIN have a Scheme implementation for complex numbers when standard C has "csin"? In Scheme, any real is also complex. That's not the case in C. I hope you're not proposing to separate the numeric types in Scheme.

Re: the future of guile

On 4 Dec, 2007, at 15:50, [EMAIL PROTECTED] wrote: 1a. Why functions like SIN have a Scheme implementation for complex numbers when standard C has "csin"? In Scheme, any real is also complex. That's not the case in C. I hope you're not proposing to separate the numeric types in Scheme.

Re: Guile-user Digest, Vol 53, Issue 14

On 26 Apr, 2007, at 18:01, [EMAIL PROTECTED] wrote: Doesn't `OPEN_BOTH' do what you want? However, the manual reads: Care should be taken with `OPEN_BOTH', a deadlock will occur if both parent and child are writing, and waiting until the write completes before doing any reading. Eac

Re: modules and C++

On 22 Mar, 2007, at 18:01, [EMAIL PROTECTED] wrote: David Fang <[EMAIL PROTECTED]> wrote: Hi, I'm having a bit of trouble using a symbol I defined in C from a module: What do I need to do to export my scm_c_define_gsubr'd functions to the module? Must I wrap them into ano

Re: let-syntax Problem

On 18 Oct, 2006, at 18:09, [EMAIL PROTECTED] wrote: ERROR: invalid syntax () ABORT: (misc-error) error. (Isn't it possible to increase the verbosity of above error message? You see, it's quite unuseful.) It seems that you are forgetting to put (use-syntax (ice-9 syncase)) before that c

Re: find s-expr in the REPL?

On 25 Sep, 2006, at 18:07, [EMAIL PROTECTED] wrote: Just to check what you mean here: in many cases a line is a single sexp, so there is no difference - so I presume you're talking about the case where a sexp is split across lines, e.g. guile> (define (foo) guile> (bar)) and saying that whe

find s-expr in the REPL?

Hi, I'd like to have the following key bindings in the REPL: - like up-arrow, but shows previous s-expr instead of last line - like ^R, but searches s-exprs instead of lines Has somebody written readline macros to do these things? Any other way? Thanks for any info, Daniel. __

Re: acosh, getting consistent results from GSL and Guile

On 18 Aug, 2006, at 18:07, [EMAIL PROTECTED] wrote: Browsing Wikipedia for acosh formulas it seems to me that GSL is using an equivalent of: (log (- x (sqrt (- (* x x) 1 while the others are using an equivalent of: (log (+ x (sqrt (- (* x x) 1 I'm interested in having equal r