Re: Hang in threads.test

2010-09-27 Thread Ludovic Courtès
Hi! Mike Gran writes: >> However, I cannot reproduce the problem with a stock 7.1 and a recent > >> CVS libgc on x86_64-linux-gnu. > > FWIW, threads.test hangs on my box as well. Before it was only > occasionally, but, lately it seems to happen all the time. Could you run the program that I p

Re: tracepoints, source breakpoints

2010-09-27 Thread Ludovic Courtès
Hi! Andy Wingo writes: > Tracepoints and breakpoints are "traps", which can enabled and disabled > and listed with the "enable", "disable", "delete", and "traps" REPL > meta-commands. > > I can also break at source locations now: > > scheme@(guile-user)> ,break-at-source "ice-9/boot-9.scm" 2

Re: set-thread-vm!

2010-09-27 Thread Andy Wingo
Hi :) On Sat 25 Sep 2010 23:49, l...@gnu.org (Ludovic Courtès) writes: > Andy Wingo writes: > >> What's the purpose of set-thread-vm! ? > > See commit 639b2eb7107b26207d13bb8acb4c1d38d7dba3bd : it is used to work > around that fact that ‘scm_call_N’ uses whatever ‘scm_the_vm’ returns, > which ma

Re: [PATCH] Performance improvement for R6RS records

2010-09-27 Thread Andy Wingo
On Mon 20 Sep 2010 09:20, Andy Wingo writes: > Will elaborate later, have to run out the door :) Do you still need some help here? I can try to work up some code to make an example. Andy -- http://wingolog.org/

Re: [PATCH] Add implementation of SRFI 27

2010-09-27 Thread Andy Wingo
On Mon 20 Sep 2010 23:10, Andreas Rottmann writes: > Here's an updated version of the patch, this time with documentation: Thanks, applied! Andy -- http://wingolog.org/

Re: Bug in documentation for `load'?

2010-09-27 Thread Andy Wingo
On Sat 25 Sep 2010 16:04, Andreas Rottmann writes: > It appears to me that the docs for `load' are wrong (both in 1.8 and > 1.9): > > -- Scheme Procedure: load filename [reader] > Load FILENAME and evaluate its contents in the top-level > environment. The load paths are not searched.

Re: set-thread-vm!

2010-09-27 Thread Ludovic Courtès
Hi! Andy Wingo writes: > On Sat 25 Sep 2010 23:49, l...@gnu.org (Ludovic Courtès) writes: > >> Andy Wingo writes: >> >>> What's the purpose of set-thread-vm! ? >> >> See commit 639b2eb7107b26207d13bb8acb4c1d38d7dba3bd : it is used to work >> around that fact that ‘scm_call_N’ uses whatever ‘scm

Re: Complex, exact numbers

2010-09-27 Thread Andy Wingo
On Mon 27 Sep 2010 00:00, Mike Gran writes: > Should a number be able to be both complex and exact? It can be in theory. However in Guile complex numbers are always inexact. Do you need exact complex numbers? It's probably possible to implement, but I don't know of any use for them. Andy -- h

Re: Complex, exact numbers

2010-09-27 Thread Mike Gran
> From: Andy Wingo > On Mon 27 Sep 2010 00:00, Mike Gran writes: > > > Should a number be able to be both complex and exact? > > It can be in theory. However in Guile complex numbers are always > inexact. > > Do you need exact complex numbers? It's probably possible to > implement, but I don

Re: Hang in threads.test

2010-09-27 Thread Neil Jerram
l...@gnu.org (Ludovic Courtès) writes: > Could you run the program that I posted and report back? That program runs fine for me - except only 100% because I have a single core. I also modified it to add continual thread creation and destruction (attached), and it was still fine. Any further ide

Re: Complex, exact numbers

2010-09-27 Thread Neil Jerram
Mike Gran writes: > Hi all- > > Should a number be able to be both complex and exact? Mathematically, I'd say yes. To argue against, you'd have to argue that i is (for some reason) inexact, and I can't see any reason for that. Neil

Re: ‘match’ and “k or more” patterns

2010-09-27 Thread Ludovic Courtès
Hi Alex, There was a bug in the patch at [0], whereby ‘..1’ would be considered as the name of a pattern variable: scheme@(guile-user)> (match '((1 2) (3 4)) (((x ..1) ...) x)) standard input:137:0: warning: possibly unbound variable `..1' standard input:137:1: In procedure module-lookup:

Re: ‘match’ and “k or more” patterns

2010-09-27 Thread Alex Shinn
On Tue, Sep 28, 2010 at 6:56 AM, Ludovic Courtès wrote: > > There was a bug in the patch at [0], whereby ‘..1’ would be considered > as the name of a pattern variable: Oh, I had already fixed that upstream (on synthcode.com), sorry I forgot to mention it! -- Alex