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 gc/gc.h in public headers I guess. (Actually,
we should inline scm_cons, too, internally.)
Agreed.
A meta-comment: can we
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
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
Hello!
Andy Wingo wi...@pobox.com 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
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 instead
Detlev Zundel d...@denx.de 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
l...@gnu.org (Ludovic Courtès) writes:
Hello,
A few more thoughts...
Andy Wingo wi...@pobox.com writes:
On Fri 25 Mar 2011 18:58, l...@gnu.org (Ludovic Courtès) writes:
Andy Wingo wi...@pobox.com writes:
bdw-gc 6.8 compatibility (hopefully)
Aarrrgh. The intent has always been to
Hello,
Andy Wingo wi...@pobox.com 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.
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
Hello!
Neil Jerram n...@ossau.uklinux.net writes:
l...@gnu.org (Ludovic Courtès) writes:
Hello,
A few more thoughts...
Andy Wingo wi...@pobox.com writes:
On Fri 25 Mar 2011 18:58, l...@gnu.org (Ludovic Courtès) writes:
Andy Wingo wi...@pobox.com writes:
bdw-gc 6.8 compatibility
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 remembered
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 version
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 this one?
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
Andy Wingo wi...@pobox.com writes:
On Mon 07 Mar 2011 21:13, Andreas Rottmann a.rottm...@gmx.at 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
Andy Wingo wi...@pobox.com 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
16 matches
Mail list logo
