Hello,
Pjotr over on guix-devel has proposed we organise a Guile developer
track at the next FOSDEM (January 2016). There seems to be a pretty
good reception on the guix mailing lists, and we're still looking for
ideas for talks, etc. If you'd be interested in giving a talk, check
out
https:
> Date: Mon, 31 Aug 2015 22:05:59 -0700
> From: Doug Evans
> Cc: Mark Kettenis ,
> "gdb-patc...@sourceware.org" , guile-devel
>
>
> On Sat, Aug 29, 2015 at 7:37 PM, Eli Zaretskii wrote:
> >> Date: Sat, 29 Aug 2015 23:04:02 +0200 (CEST)
> >> From: Mark Kettenis
> >> CC: e...@gnu.org, gd
On Tue, Sep 1, 2015 at 7:35 AM, Eli Zaretskii wrote:
>> The goal here is to block these signals from being sent to the threads
>> that Guile (or more specifically libgc) creates.
>
> Why only libgc? Don't we want to block these signals in any Guile
> code invoked later by GDB?
Any threads create
> Date: Tue, 1 Sep 2015 08:22:44 -0700
> From: Doug Evans
> Cc: Mark Kettenis ,
> "gdb-patc...@sourceware.org" , guile-devel
>
>
> On Tue, Sep 1, 2015 at 7:35 AM, Eli Zaretskii wrote:
> >> The goal here is to block these signals from being sent to the threads
> >> that Guile (or more sp
Oops, it looks like the test suite doesn't pass anymore after I fixed
the problem where I was mutating a literal bytevector. It should have
been the other way around! :-)
So a #u8() and #vu8() aren't the same thing after all.
(u8vector? #vu8(0)) => #f
(u8vector? (make-bytevector 1))
taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes:
> How about making 'foo turn into something like (__quote__ foo), and
> similar for `foo, #'foo, etc.?
This is part of the standard behavior of 'read', e.g. section 4.3.5 of
the R6RS, and has been for over 50 years. Lots of existin
