Unexpected srfi-4 C Interface Change in 2.0.10

2014-03-19 Thread Barry Fishman
When building C interface code using scm_f32vector_writable_elements() in 2.0.10 and on the trunk I found: For a vector generated in guile with: (f32vector 0.25 0.25 0.25 1.0) I found in the C interface: scm_t_array_handle handle; size_t vlen, vinc; float *arrayp; arrayp = scm_f32v

Re: Unexpected srfi-4 C Interface Change in 2.0.10

2014-03-19 Thread Mark H Weaver
Daniel Llorens writes: >> Message: 2 >> Date: Wed, 19 Mar 2014 10:22:40 -0400 >> From: Barry Fishman >> To: guile-devel@gnu.org >> Subject: Unexpected srfi-4 C Interface Change in 2.0.10 >> Message-ID: >> Content-Type: text/plain >> >> When building C interface code using scm_f32vector_writabl

Unexpected srfi-4 C Interface Change in 2.0.10

2014-03-19 Thread Daniel Llorens
> Message: 2 > Date: Wed, 19 Mar 2014 10:22:40 -0400 > From: Barry Fishman > To: guile-devel@gnu.org > Subject: Unexpected srfi-4 C Interface Change in 2.0.10 > Message-ID: > Content-Type: text/plain > > When building C interface code using scm_f32vector_writable_elements() > in 2.0.10 and on t

Re: Unexpected srfi-4 C Interface Change in 2.0.10

2014-03-19 Thread Andy Wingo
Hi, I'm very sorry about this breakage to the SRFI-4 C interface. I've pushed a fix (2be7131ee0c38336483226657872a8faa62a2562) and a test case and we'll roll another release shortly; perhaps tomorrow. Apologies again. Regards, Andy -- http://wingolog.org/