Re: compiling with -DSCM_DEBUG=1

Hi Ken, I've been trying to reproduce the guardian finalisation problem that you see with SCM_DEBUG==1 but, like Ludovic, I haven't had any luck. With SCM_DEBUG=1 for the whole build (plus the SCM_GC_MARK_P change), I'm afraid my machine grinds to a halt when it gets to goops.c - i.e. it never fi

Re: psyntax error reporting bug

Hi Ludo, > Andy is the expert, but I think such a patch can’t hurt, so please do! Done! See attached. Regards, Julian From 48128b32d7f9d9613e46b61a3c695d786152fb67 Mon Sep 17 00:00:00 2001 From: Julian Graham Date: Sun, 18 Oct 2009 17:56:13 -0400 Subject: [PATCH] Fix typo in psyntax.scm relat

Re: upcoming patches

Andy Wingo writes: > 2) Make sure Mark's patch is in > > If Neil gets to this one first, that's fine :) But it needs to go > in, so that Have I missed this? I _think_ I'm still waiting for Mark's updated patch... Many apologies in advance if I have missed it! Regards, Neil

Re: psyntax error reporting bug

Hello! Julian Graham writes: > I'm no psyntax expert, but it looks like there's a minor typo in our > psyntax implementation. In psyntax.scm, at line 1325 (in > `chi-macro'), the expression: > > (syntax-violation #f "encountered raw symbol in macro output" > (source-wrap e w s mod) x) > > ...sh

psyntax error reporting bug

Hi Guilers, I'm no psyntax expert, but it looks like there's a minor typo in our psyntax implementation. In psyntax.scm, at line 1325 (in `chi-macro'), the expression: (syntax-violation #f "encountered raw symbol in macro output" (source-wrap e w s mod) x) ...should read: (syntax-violation #f

Readline init broke on master

Hi- If I start up an interactive session with the current master, and I enter the following three lines at the prompt (use-modules (ice-9 readline)) (activate-readline) I get an infinite loop of ERROR: Wrong number of arguments to # Thanks, Mike

Compiled load path issues

Hello! Once upon a time, if ‘chbouib.go’ is in the vicinity of ‘chbouib.scm’, then ‘(use-modules (chbouib))’ would load ‘chbouib.go’. This is no longer the case, but can be remedied with something like this: diff --git a/libguile/load.c b/libguile/load.c index 50af256..194d1e5 100644 --- a/libgu

Re: frozen!

Hello, Andy Wingo writes: > My only concern is with bytevectors. It should be possible to map a > bytevector to an existing range of memory, for read-write access. That > implies a pointer indirection. We can optimize for the inline case by > doing something like: > >++--+-+.

Re: frozen!

Hi Ludo, On Tue 06 Oct 2009 23:49, l...@gnu.org (Ludovic Courtès) writes: > - bdw-gc-static-alloc (need to grep through sources to estimate the > amount of breakage it would cause) Neat :) My only concern is with bytevectors. It should be possible to map a bytevector to an existing range

upcoming patches

My todo list, for the record: 1) Finish case-lambda branch -- should be a day or two's work there This doesn't necessarily imply that all the new features (case-lambda, lambda*, ...) are fully baked, but the VM, debugging, and IL support for the features should be mergeable and d

Re: GNU Guile 1.9.4 released (alpha)

On Fri 16 Oct 2009 00:31, l...@gnu.org (Ludovic Courtès) writes: > We are pleased to announce GNU Guile release 1.9.4. Thanks for doing the release, again! :-) Andy -- http://wingolog.org/

Re: frozen!

Hi Mike, On Tue 06 Oct 2009 23:35, Mike Gran writes: >> From: Andy Wingo >> Subject: frozen! > > I need to roll back the changes made to i18n.c > that made locale-specific case conversion of strings > work on GNU but break on Darwin. Locale-specific > case conversion of strings works, but only