Daniel Llorens writes:
> The only generalized-vector-? function that doesn't have a direct
> array-? correspondence is generalized-vector-length. However, even for
> arrays of rank > 1 it is often convenient to have a function such as
>
> (array-length a) = (car (array-dimensions a))
>
> or maybe
Hi guys,
It was brought to my attention on #guile that the listen option no
longer works in guile.
$ guile --listen
ice-9/psyntax.scm:1201:48: In procedure syntax-type:
ice-9/psyntax.scm:1201:48: Syntax error:
unknown location: source expression failed to match any pattern in form (@@
On 09/19/2012 12:51 PM, Ian Price wrote:
Hi guys,
It was brought to my attention on #guile that the listen option no
longer works in guile.
Ouch. That's a serious regression in guile 2.0.6.
I think the relevant commit is a March 8th commit by Mark Weaver
(8210c85), which restricts @@ to id
On Sep 19, 2012, at 18:00, guile-devel-requ...@gnu.org wrote:
> Date: Wed, 19 Sep 2012 13:02:25 +0100
> From: Peter TB Brett
> To: guile-devel@gnu.org
> Subject: Re: propose deprecation of generalized-vector-*
...
> It seems to me that array-length should return the first non-unity
> dimensio
Mark H Weaver writes:
> Your fixes look good to me. It would be good to add tests for the
> listen option also.
(system repl server) does need tests, no question. But, I'm not sure how
I would test the command-line stuff. I suppose we could run a guile
instance with various arguments, have it o
I have found the cause of the second problem, but I'm not sure what to
do about it. Here's what's happening:
libguile/bytevectors.c includes .
uniconv.h lives in my system include directory
(~/.nix-profile/include, actually). It includes a file called
"unitypes.h". That refers to ~/.nix-profile/i
