From: Andreas Rottmann <a.rottmann@gmx.at>
Cc: g-wrap-dev@nongnu.org, guile-devel@gnu.org
Subject: Re: SRFI 50: Mixing Scheme and C
Date: Fri, 13 Feb 2004 20:57:36 +0100 [thread overview]
Message-ID: <87u11ug3bj.fsf@alice.rotty.yi.org> (raw)
In-Reply-To: <873c9erjd4.fsf@raven.defaultvalue.org> (Rob Browning's message of "Fri, 13 Feb 2004 11:15:35 -0600")
Rob Browning <rlb@defaultvalue.org> writes:
> Dale brought this to my attention, and I haven't had a chance to read
> it carefully yet, but I thought others might want to take a look as
> well.
>
> http://srfi.schemers.org/srfi-50/srfi-50.html
>
I've read some of the discussion on the mailing list, and I find Tom
Lord's arguments regarding deficiencies of the SRFI draft quite sound
(disclaimer: I recently had a look at and did a little bit of hacking
on Pika, Tom Lord's scheme project).
Regarding G-Wrap: it would certainly be a plus to be more language (or
C Scheme API) agnostic. Incidencially, I just started an experimental
branch of G-Wrap, in wich I'll try to come up with a
language-agnostic, GOOPS-based design for G-Wrap and then build a
compatibility layer (offering the current wrapping API) upon it. The
project is currently in the draft phase (but there is already a
g-wrap--tng branch in my archive; tng stands for "The Next Generation"
;-).
Cheers, Andy
--
Andreas Rottmann | Rotty@ICQ | 118634484@ICQ | a.rottmann@gmx.at
http://yi.org/rotty | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
Say NO to Software Patents! -- http://petition.eurolinux.org/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-02-13 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 17:15 SRFI 50: Mixing Scheme and C Rob Browning
2004-02-13 19:57 ` 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=87u11ug3bj.fsf@alice.rotty.yi.org \
--to=a.rottmann@gmx.at \
--cc=g-wrap-dev@nongnu.org \
--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).