unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: heads up: goops class export
Date: Tue, 03 May 2011 14:19:43 +0200	[thread overview]
Message-ID: <87sjswnfhc.fsf@gnu.org> (raw)
In-Reply-To: <m3pqo0ruzb.fsf@unquote.localdomain> (Andy Wingo's message of "Tue, 03 May 2011 11:31:20 +0200")

Hello!

Andy Wingo <wingo@pobox.com> writes:

> On Tue 03 May 2011 10:50, ludo@gnu.org (Ludovic Courtès) writes:
>
>> Andy Wingo <wingo@pobox.com> 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 agree that they should not be exported from (oop goops).
>>
>> However, how should GOOPS users access these classes then?  There needs
>> to be a way to get the class object associated with a SMOB type, for
>> instance.
>
> Hum, a good question!  Perhaps smob-name->class,

Yes, why not.  (It’s equivalent to (@@ (oop goops) foobar) in terms of
providing access to everyone, though.)

Thanks,
Ludo’.



  reply	other threads:[~2011-05-03 12:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-01 20:32 heads up: goops class export Andy Wingo
2011-05-03  8:50 ` Ludovic Courtès
2011-05-03  9:31   ` Andy Wingo
2011-05-03 12:19     ` Ludovic Courtès [this message]
2011-05-03 13:11       ` Andy Wingo
2011-07-01 10:03 ` 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=87sjswnfhc.fsf@gnu.org \
    --to=ludo@gnu.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).