From: Andreas Rottmann <a.rottmann@gmx.at>
Cc: Mikael Djurfeldt <djurfeldt@nada.kth.se>,
Marius Vollmer <mvo@zagadka.de>,
guile-devel@gnu.org
Subject: Re: C API for goops
Date: 10 Aug 2002 13:36:16 +0200 [thread overview]
Message-ID: <87eld7osi7.fsf@alice.rhinosaur.lan> (raw)
In-Reply-To: <20020809111905.GA25401@www>
>>>>> "rm" == rm <rm@fabula.de> writes:
rm> On Fri, Aug 09, 2002 at 11:51:00AM +0200, Mikael Djurfeldt
rm> wrote:
>> What's the status on the C API for goops? I'm thinking on the
>> API for specifying and creating Goops objects and defining and
>> invoking methods from C code .
rm> Are you thinking about it or do you intent to work on it :-)))
rm> It would be _really_ nice to be able to provide goops objetcs
rm> and generic methods from the C side.
This is already possible i have quite some code lying around that does
* method creation
* generic function creation
* class creation
and probably some more. It took my quite some time to figure it all
out (mostly by studying the goops C code) and it probably is not very
clean (depends on GOOPS internals) in some places. However, it works,
but is not very useful due to the goops-1 bug :-(
You can have a look most of the code at [1]. Note that it is C++. YMMV.
[1] http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ucxx/yehia/ucxx/languages/guile/guile-script.cc?rev=HEAD&content-type=text/vnd.viewcvs-markup
Regards, Andy
--
Andreas Rottmann | Dru@ICQ | 118634484@ICQ | a.rottmann@gmx.at
http://www.8ung.at/rotty | GnuPG Key: http://www.8ung.at/rotty/gpg.asc
Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-08-10 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 9:51 C API for goops Mikael Djurfeldt
2002-08-09 11:19 ` rm
2002-08-09 13:34 ` Mikael Djurfeldt
2002-08-10 11:36 ` Andreas Rottmann [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=87eld7osi7.fsf@alice.rhinosaur.lan \
--to=a.rottmann@gmx.at \
--cc=djurfeldt@nada.kth.se \
--cc=guile-devel@gnu.org \
--cc=mvo@zagadka.de \
/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).