From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: guile-devel@gnu.org
Subject: Re: Initial SCTP support for the upcoming 1.6.5 release
Date: Tue, 24 Aug 2004 16:24:24 +0200 [thread overview]
Message-ID: <lj6578haw7.fsf@troy.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <95CA6528-F5CB-11D8-93F2-000D932C78D8@lurchi.franken.de> (Michael Tuexen's message of "Tue, 24 Aug 2004 14:46:14 +0200")
Michael Tuexen <Michael.Tuexen@lurchi.franken.de> writes:
> with the hints of Kevin I got my stuff working.
Excellent, and please accept my apologies for doing such a louse job
with the first attempt. I forgot to include sctp.scm in the tarball,
here it is for reference:
(define-module (net sctp))
(export sctp-recvmsg!
sctp-sendmsg
SOCK_SEQPACKET
IPPROTO_SCTP
IPPROTO_TCP
IPPROTO_UDP
MSG_UNORDERED
MSG_ADDR_OVER
MSG_ABORT
MSG_EOF
MSG_EOR
MSG_NOTIFICATION
MSG_PR_SCTP_TTL
MSG_PR_SCTP_BUF)
(load-extension "libguile-net-sctp" "net_sctp_init")
> I need besides the static functions from socket.c the
> SCM_SYSCALL stuff from libguile/_scm.h. This is file is
> not installed. So is there a chance to move the SCM_SYSCALL
> stuff from _scm.h to __scm.h? If not, I have to duplicate
> the code, which is not a problem...
Yes, please duplicate. SCM_SYSCALL is more of an internal helper for
boilerplate code that unrelated to Guile.
> I have another question: How can I make the documentation included
> in the SCM_DEFINE makro available from scheme.
I don't think there is a good way yet. Which is really bad, bad, bad,
I know. Leave your docstring in place and hope that you will soon be
able to use it.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-08-24 14:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 18:26 Initial SCTP support for the upcoming 1.6.5 release Michael Tuexen
2004-08-11 12:29 ` Michael Tuexen
2004-08-13 13:40 ` Marius Vollmer
2004-08-13 20:27 ` Michael Tuexen
2004-08-24 14:15 ` Marius Vollmer
2004-08-24 17:35 ` Michael Tuexen
2004-09-08 15:03 ` Marius Vollmer
2004-09-08 15:34 ` Michael Tuexen
2004-08-14 9:59 ` Michael Tuexen
2004-08-16 0:40 ` Kevin Ryde
2004-08-16 10:42 ` Michael Tuexen
2004-08-17 23:46 ` Kevin Ryde
2004-08-19 18:34 ` Michael Tuexen
2004-08-20 1:13 ` Kevin Ryde
2004-08-20 7:57 ` Michael Tuexen
2004-08-16 17:02 ` Michael Tuexen
2004-08-16 18:44 ` Rob Browning
2004-08-20 18:18 ` Michael Tuexen
2004-08-23 0:58 ` Kevin Ryde
2004-08-23 19:54 ` Michael Tuexen
2004-08-24 0:57 ` Kevin Ryde
2004-08-24 11:27 ` Michael Tuexen
2004-08-24 12:46 ` Michael Tuexen
2004-08-24 14:24 ` Marius Vollmer [this message]
2004-08-24 18:22 ` Michael Tuexen
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=lj6578haw7.fsf@troy.dt.e-technik.uni-dortmund.de \
--to=marius.vollmer@uni-dortmund.de \
--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).