Hi :)
On Thu 30 Jun 2011 23:46, l...@gnu.org (Ludovic Courtès) writes:
> http://lists.r6rs.org/pipermail/r6rs-discuss/2007-March/thread.html#1856
Wow, forgot about that one ;)
> Here’s another argument: these macros are about writing imperative code,
> which, as we all know, is Evil. As such
Hi!
Thanks for thinking this through!
On Thu 30 Jun 2011 23:27, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo skribis:
>
>> 4) Our fluids currently have problems with threads: if a thread not
>> spawned by a Guile thread enters Guile, its fluids are bound to
>> #f. This shoul
Hi,
On Thu 30 Jun 2011 23:37, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo skribis:
>
>> After some thinking, the base thing to do is just to add a warning port,
>> and make warnings (non-fatal informative messages) write to that port.
>> I have done this in the attached patches. Any obj
Hi,
On Sun 01 May 2011 22:32, Andy Wingo writes:
> Currently when you define a SMOB type or set a name on a vtable, a
> corresponding class is automatically exported from (oop goops). This
> breaks modularity, and I think we should stop doing it in 2.2.
>
> I will make this change at some point
Hi nalingarut,
On Mon 13 Jun 2011 05:54, nalaginrut writes:
> scheme@(guile-user)> (define aaa (@ (rnrs) unless))
> While compiling expression:
> ERROR: Syntax error:
> unknown location: source expression failed to match any pattern in form
> unless
As Ian said it's expected. It would work lik
Hello!
On Fri 06 May 2011 07:51, CRLF0710 writes:
> Version: 2.0.1
>
> ' (a #{.}# b)
> $1 = (a . b)<= dot as cons ?
Good catch! Fixed in git.
Thanks,
Andy
--
http://wingolog.org/
Hi Mark!
On Mon 23 May 2011 21:42, Mark H Weaver writes:
> The tentative plan is to use normal strings to represent pathnames,
> command-line arguments, environmental variable values, and other such
> POSIX byte strings.
Apologies for not giving you prompt feedback on this idea. Basically I
th
Heya BT,
On Fri 27 May 2011 03:42, BT Templeton writes:
> Are the scm_remember_upto_here_* functions useful now that Guile uses
> BDW-GC?
Yes they are. If you have a pointer to a field of an object with a
destructor, and GCC kills the reference to the object, it could be
collected.
Actually w
Greets,
On Sun 08 May 2011 16:34, l...@gnu.org (Ludovic Courtès) writes:
> writes:
>
>> Recent changes to stable-2.0 seem to cause a deadlock in scwm. Here is the
>> last 10 frames of a backtrace.
These are fixed.
> I’m not sure if this is related
It's not :)
> but there’s this new error t
On Fri 06 May 2011 16:21, writes:
> I've been slowly (very slowly!) debitrotting scwm.
Cool! I've been (very slowly!) catching up to the present with regards
to guile-devel.
> There is currently a deprecation warning for scm_internal_stack_catch.
> The warning says to talk to guile-devel. So
Andy Wingo skribis:
> Basically I appreciate the concerns but have not found a way to solve
> the whole problem nicely, so I kept it simple. As it seems we agree on
> the need for higher-level solutions based on a warning port accessible
> in (guile) and C, I'm going to see about committing some
Andy Wingo skribis:
> One place you might want to use them though is in type checks for Scheme
> code. We currently don't do very much of that, but probably should in
> the future. As in:
>
> (define (parameter-fluid p)
> (unless (parameter? p) (wrong-type-arg p 'parameter))
> (struct
Hello!
Andy Wingo skribis:
> Third time's the charm, as they say... here's the deal. `with-fluids'
> is fairly efficient, because its body does not need to be allocated as a
> closure, but it doesn't provide you any guarantees about the values
> bound to the fluids. Parameter objects are bette
Hi!
On Fri 01 Jul 2011 15:04, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo skribis:
>
>> here's the deal.
I think I just read three emails of mine with this phrase in it.
Terrible. I promise more syntactic variability in the future.
>> (with-fluids ((%current-input-port 'foo)) ...) ?
On Fri 17 Jun 2011 11:03, Andy Wingo writes:
> The libgc list is g...@linux.hpl.hp.com. I have found the libgc
> maintainers to be very responsive. If there is a problem with mingw and
> threads that is fixed by Jan's patches, I'm sure they would be happy to
> have them. Who will submit them t
Hello,
As seen in ccb80964cd7cd112e300c34d32f67125a6d6da9a, there’s a lock
ordering mismatch between ‘do_thread exit’ and ‘fat_mutex_lock’
wrt. ‘t->admin_mutex’ and ‘m->lock’.
I thought this commit solved the problem, but now I think it doesn’t
because it leaves a small window during which a mute
Andy Wingo writes:
>> $1 = (a . b)<= dot as cons ?
>
> Good catch! Fixed in git.
It is to my discredit that I fixed this for myself a few weeks back and
never remembered to send it to the mailing list, but too late for that
now ...
--
Ian Price
"There are only two hard problems in Compute
We are pleased to announce GNU Guile release 2.0.2, the next maintenance
release for the 2.0.x stable series.
The Guile web page is located at http://gnu.org/software/guile/ .
Guile is an implementation of the Scheme programming language, with
support for many SRFIs, packaged for use in a wide va
18 matches
Mail list logo
