From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user@gnu.org
Subject: Re: one C function to many Scheme functions
Date: 09 Jan 2003 23:30:36 +0000 [thread overview]
Message-ID: <m34r8hlx43.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <20030109102622.GA7713@kolos.math.uni.lodz.pl>
>>>>> "Krzysztof" == Krzysztof Garus <bajcik@kolos.math.uni.lodz.pl> writes:
Krzysztof> I am using similar workaround on similar concept, also
Krzysztof> with definitions.
Krzysztof> Last question: what is cost this definition? I suppose
Krzysztof> it is small, but if I call Scheme callback very
Krzysztof> frequent?
I doubt it's significant; anyway performance questions normally make
sense only in the context of a particular application. If you do find
it's a slow point, ask here again.
Neil
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-01-09 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 20:30 one C function to many Scheme functions bajcik
2003-01-08 20:45 ` Neil Jerram
2003-01-09 10:26 ` Krzysztof Garus
2003-01-09 23:30 ` Neil Jerram [this message]
2003-01-09 11:40 ` Matthias Koeppe
2003-01-09 23:19 ` Neil Jerram
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=m34r8hlx43.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-user@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).