Re: bdw-gc includes in libguile.h

2011-03-28 Thread Andy Wingo
Greets :) On Sun 27 Mar 2011 17:11, l...@gnu.org (Ludovic Courtès) writes: > Internally we should still inline scm_cell & co., though; that can be > done without exposing in public headers I guess. (Actually, > we should inline scm_cons, too, internally.) Agreed. >>> A meta-comment: can we ag

Compilation error with stable-2.0 branch

2011-03-28 Thread Detlev Zundel
Hi, compiling TOT of this branch (commit 9dadfa47b07548ff5cf3604067910c8aece93c42 [fix prompt in fix in single-value context compilation]) fails like this: make[2]: Entering directory `/opt/src/git/guile/libguile' make all-am make[3]: Entering directory `/opt/src/git/guile/libguile' CCLD gui

Re: [PATCH] Add `fixnum?' VM primitive

2011-03-28 Thread Ken Raeburn
On Mar 25, 2011, at 06:40, Ludovic Courtès wrote: > I guess we could even add the new opcode in stable-2.0 because Andy > tweaked objcode version check to be smarter—i.e., 2.0.1 would be able to > read objcodes produced by either 2.0.1 or 2.0.0. If I switch from a machine with 2.0.1 installed to a

Re: bdw-gc includes in libguile.h

2011-03-28 Thread Ludovic Courtès
Hello! Andy Wingo writes: >>> Sure. Sorry for the precipitous action. That said, this bug has been >>> open since September: https://savannah.gnu.org/bugs/?32436 >> >> Oh indeed, I hadn’t realized there’s a connection; still... > > Do you have any thoughts on that bug, The problem is that li

Re: bdw-gc includes in libguile.h

2011-03-28 Thread Andy Wingo
Greets :) On Mon 28 Mar 2011 21:22, l...@gnu.org (Ludovic Courtès) writes: > The problem is that libgc ends up being initialized behind our back upon > the first libgc-redirected ‘pthread_create’ call. Indeed. > Hans Boehm suggested [0] two solutions: > > 1. Disable pthread redirects and inst

Re: Compilation error with stable-2.0 branch

2011-03-28 Thread Neil Jerram
Detlev Zundel writes: > Hi, > > compiling TOT of this branch (commit > 9dadfa47b07548ff5cf3604067910c8aece93c42 [fix prompt in fix in > single-value context compilation]) fails like this: > > make[2]: Entering directory `/opt/src/git/guile/libguile' > make all-am > make[3]: Entering directory `/

Re: [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.0-124-g5f0d295

2011-03-28 Thread Neil Jerram
l...@gnu.org (Ludovic Courtès) writes: > Hello, > > A few more thoughts... > > Andy Wingo writes: > >> On Fri 25 Mar 2011 18:58, l...@gnu.org (Ludovic Courtès) writes: >> >>> "Andy Wingo" writes: >>> bdw-gc 6.8 compatibility (hopefully) >>> >>> Aarrrgh. The intent has always been to su

Re: bdw-gc includes in libguile.h

2011-03-28 Thread Ludovic Courtès
Hello, Andy Wingo writes: > On Mon 28 Mar 2011 21:22, l...@gnu.org (Ludovic Courtès) writes: > >> The problem is that libgc ends up being initialized behind our back upon >> the first libgc-redirected ‘pthread_create’ call. > > Indeed. > >> Hans Boehm suggested [0] two solutions: >> >> 1. Disa

Re: PEG Patches

2011-03-28 Thread Noah Lavine
Hi, > I think the solution is to confront the circularity directly.  It exists > because the PEG s-exp grammar also deals with the string grammar, which > needs an already-build PEG parser. > > Let's break it instead into layers without cycles: removing the string > grammar from the s-exp code gen

Re: [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.0-124-g5f0d295

2011-03-28 Thread Ludovic Courtès
Hello! Neil Jerram writes: > l...@gnu.org (Ludovic Courtès) writes: > >> Hello, >> >> A few more thoughts... >> >> Andy Wingo writes: >> >>> On Fri 25 Mar 2011 18:58, l...@gnu.org (Ludovic Courtès) writes: >>> "Andy Wingo" writes: > bdw-gc 6.8 compatibility (hopefully) >

Re: PEG Patches

2011-03-28 Thread Noah Lavine
> I've been working on that. The attached two patches break the > circularity. The code still isn't organized brilliantly, but after > applying these I think we would only want pretty minor cleanups before > merging PEG into the main branch. Actually, forget this bit. I wrote it before I remembere

Re: [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.0-124-g5f0d295

2011-03-28 Thread Mike Gran
> > What is the current best recommendation for libgc to use? > > 7.x.  Best recommendation would be 7.2, which fixes several bugs, but it > hasn’t been released yet, unfortunately. Partially related to all of this is that there are compilation issues on Cygwin.  Cygwin runs bdw-gc 7.1.  That ver

Re: [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.0-124-g5f0d295

2011-03-28 Thread Neil Jerram
l...@gnu.org (Ludovic Courtès) writes: > 7.x. Best recommendation would be 7.2, which fixes several bugs, but it > hasn’t been released yet, unfortunately. > >> (Note in particular that Guile doesn't build with one of the most recent >> releases, 7.2alpha4. > > Really? What’s the problem with th

Re: PEG Patches

2011-03-28 Thread Michael Lucy
A variant on the second option would be first defining peg-string-compile to just throw an error, then redefining it later to actually compile the string. That seems a little less hackish, at least to me. A fifth option would be to make peg-sexp-compile take an optional argument FUN-RECUR that it

Re: CPAN for Guile

2011-03-28 Thread Andreas Rottmann
Andy Wingo writes: > On Mon 07 Mar 2011 21:13, Andreas Rottmann writes: > >> I'm (very slowly) working on getting dorodango[0] to work on Guile. In >> principle, nothing in Dorodango is inherently tied to R6RS -- it should >> very reasonably be possible to use it for Guile-specific packages as

Re: summer of code project: cpan

2011-03-28 Thread Andreas Rottmann
Andy Wingo writes: > Hello all, > > Now that GNU is in the Google SoC, I'd like to propose again a CPAN for > Guile. (It does needs a proper name, but that name doesn't have to > correspond to the name of the command-line utility; see my other mail > about "guido".) > > The proposal would be to