unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: Inheriting from foreign objects
Date: 10 Apr 2002 20:47:13 +0100	[thread overview]
Message-ID: <m3lmbvwd32.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <873cy47mxs.fsf@alice.rhinosaur.lan>

>>>>> "Andreas" == Andreas Rottmann <a.rottmann@gmx.at> writes:

    Andreas> Hi!
    Andreas> I have run into a problem: I create classes from C (C++) using
    Andreas> scm_make_class(). These classes all get the SCM_CLASSF_FOREIGN bit set
    Andreas> to treat them as foreign objects (like invoke the constructor &
    Andreas> desctructor supplied). 

    Andreas> So far, so good. However, when I derive from these classes (on the
    Andreas> Scheme level), the new class has also the FOREIGN bit set (it's
    Andreas> inherited in scm_sys_inherit_magic_x(), AFAICT), but the constructor
    Andreas> set NULL, which causes %allocate-instance bails out when trying to
    Andreas> instantiate the class.

    Andreas> Is there a way I can cleanly derive from C-created classes?

I'd say you're in virgin territory here, and that any advice you can
give on such problems, and on defining a C API for GOOPS, would be
very useful.

(Sorry that wasn't much help!  Good luck.)

        Neil


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-04-10 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09 18:21 Inheriting from foreign objects Andreas Rottmann
2002-04-10 19:47 ` Neil Jerram [this message]
2002-04-23 20:43   ` Thien-Thi Nguyen
2002-04-30 10:23     ` Andreas Rottmann
2002-05-15 12:30       ` Thien-Thi Nguyen

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=m3lmbvwd32.fsf@laruns.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    /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).