From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org, guile-user@gnu.org
Subject: Re: Inheriting from foreign objects
Date: Wed, 15 May 2002 05:30:42 -0700 [thread overview]
Message-ID: <E177xvW-0000bQ-00@giblet> (raw)
In-Reply-To: <874rht7aet.fsf@alice.rhinosaur.lan> (message from Andreas Rottmann on 30 Apr 2002 12:23:06 +0200)
From: Andreas Rottmann <a.rottmann@gmx.at>
Date: 30 Apr 2002 12:23:06 +0200
I suggest you write some 'test' code that uses the various
goops-related C functions, as that would both make them easier to
understand and they can be validated this way.
i've added "write goops test cases in C" under "Eventually" in the TODO.
> [cc guile-user in order to ask survey question: which goops-related C
> functions do people use now? the answer to this helps shape definition
> of the C interface to goops -- thanks!]
>
I use, in my C++ <-> GOOPS bindings: [...]
recorded in $workbook/policy/api.text -- thanks.
BTW: Has anybody of the developers looked at my GOOPS-related
bugreport yet? Since I have included a program documenting the bug it
shouldn't be too hard to investigate...
i believe this is bug `goops-1'.
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-05-15 12:30 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
2002-04-23 20:43 ` Thien-Thi Nguyen
2002-04-30 10:23 ` Andreas Rottmann
2002-05-15 12:30 ` Thien-Thi Nguyen [this message]
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=E177xvW-0000bQ-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=ttn@glug.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).