From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Cc: guile-devel@gnu.org
Subject: Re: Initial SCTP support for the upcoming 1.6.5 release
Date: Tue, 24 Aug 2004 13:27:10 +0200 [thread overview]
Message-ID: <89D0BF0E-F5C0-11D8-93F2-000D932C78D8@lurchi.franken.de> (raw)
In-Reply-To: <87vff9z737.fsf@zip.com.au>
Kevin,
see my comments below.
Best regards
Michael
On Aug 24, 2004, at 2:57 AM, Kevin Ryde wrote:
> Michael Tuexen <Michael.Tuexen@lurchi.franken.de> writes:
>>
>> Since the set/getsockopt function does not reference any specific
>> structure
>> it would be a possibility of have it provided as generic as it is in C
>> and
>> I would write some scheme functions to transfer the SCTP specific data
>> into the generic one.
>
> It's probably better to make replacement functions that do their
> specifics then call the core.
>
> (If there were many semi-independent modules going to do that then
> some sort of hook arrangement would be better, but a replacement will
> work initially at least.)
So I just define my own setsockopt and it will 'overwrite' the existing
one. That'll work. I was not sure if I can just define another function
with the same name and that will overwrite the existing one.
>
>> I have not found an example for C based modules for guile yet.
>
> load-extension I think, per "A Sample Guile Extension" and "Putting
> Extensions into Modules" in the manual. More indexing in the manual
> might help when looking for such stuff.
I was looking at
http://www.gnu.org/software/guile/docs/guile-ref/Dynamic-
Libraries.html#Dynamic%20Libraries
under the title "Modules"
not at "A Whirlwind Tour" where I find under
http://www.gnu.org/software/guile/docs/guile-ref/A-Sample-Guile-
Extension.html#A%20Sample%20Guile%20Extension
the Extension stuff... Thank you very much for the hint.
>
>> Everything distributed with guile is scheme based, I think.
>
> Cf srfi/srfi-13 and 14, and guile-readline/ice-9/readline.scm.
Ahh. I have not found them. I was looking at ice-9...
Thank you very much for your help.
>
_______________________________________________
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 11:27 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 [this message]
2004-08-24 12:46 ` Michael Tuexen
2004-08-24 14:24 ` Marius Vollmer
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=89D0BF0E-F5C0-11D8-93F2-000D932C78D8@lurchi.franken.de \
--to=michael.tuexen@lurchi.franken.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).