cvs srfi-1 for-each segv

cvs srfi-1 for-each segv

[Kevin Ryde]

Something has broken in the srfi-1 for-each.  Eg.

	(use-modules (srfi srfi-1))
	(for-each noop '(1 2 3) '(4 5) '())
	=> seg fault

Bit of a trace and some printfs suggest maybe the lists are mangled
somehow by SCM_SIMPLE_VECTOR_REF, though I don't see how.  Are you
supposed to use that macro with an scm_vector result now?


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel

Re: cvs srfi-1 for-each segv

[Marius Vollmer]

Kevin Ryde <user42@zip.com.au> writes:

> Something has broken in the srfi-1 for-each.  Eg.
>
> 	(use-modules (srfi srfi-1))
> 	(for-each noop '(1 2 3) '(4 5) '())
> 	=> seg fault


Oops, I made a small typo when changing the code to use
SCM_SIMPLE_VECTOR_REF.

2005-01-10  Marius Vollmer  <mvo@zagadka.de>

	* srfi-1.c (check_args): Bugfix to change from 2005-01-02: ARGV is
	the vector to check, not ARGS.

> Bit of a trace and some printfs suggest maybe the lists are mangled
> somehow by SCM_SIMPLE_VECTOR_REF, though I don't see how.  Are you
> supposed to use that macro with an scm_vector result now?

Yes, scm_vector is guaranteed to return a simple vector, and you can
use SCM_SIMPLE_VECTOR_REF with the result.  You can also use
scm_c_vector_ref, of course, or scm_vector_elements +
scm_array_handle_release.

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel