unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Ken Raeburn <raeburn@raeburn.org>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [Guile-commits] GNU Guile branch, goops-cleanup, created. release_1-9-4-72-gb1955b1
Date: Mon, 23 Nov 2009 03:05:56 -0500	[thread overview]
Message-ID: <368BC133-C020-4554-9097-CF32496F1416@raeburn.org> (raw)
In-Reply-To: <m31vjreo0y.fsf@pobox.com>

On Nov 21, 2009, at 13:22, Andy Wingo wrote:
>>> It's confusing a bit, and delightful :) See
>>> http://wingolog.org/pub/goops-inline-slots.png.
>>
>> Nice diagram! :-)
>
> Followed up by
> http://wingolog.org/archives/2009/11/09/class-redefinition-in-guile :)

Nice description.

But, I'm looking at it, and thinking... is that widget update done in  
a thread-safe manner?

Ken




  reply	other threads:[~2009-11-23  8:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1N5STy-0005mm-2g@cvs.savannah.gnu.org>
2009-11-05 18:13 ` [Guile-commits] GNU Guile branch, goops-cleanup, created. release_1-9-4-72-gb1955b1 Ludovic Courtès
2009-11-05 23:35   ` Andy Wingo
2009-11-08  0:41     ` Ludovic Courtès
2009-11-21 18:22       ` Andy Wingo
2009-11-23  8:05         ` Ken Raeburn [this message]
2009-11-24 22:29           ` Andy Wingo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=368BC133-C020-4554-9097-CF32496F1416@raeburn.org \
    --to=raeburn@raeburn.org \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).