From: Mike Gran <spk121@yahoo.com>
To: "Jason R. Green" <jg525@cam.ac.uk>, guile-devel@gnu.org
Subject: Re: Guile and GSL
Date: Sun, 7 Mar 2010 11:41:34 -0800 (PST) [thread overview]
Message-ID: <586212.40078.qm@web37907.mail.mud.yahoo.com> (raw)
In-Reply-To: <debdc5451003070438p74af9f3bh769fa5da49a5be38@mail.gmail.com>
> From: Jason R. Green jg525@cam.ac.uk
I'm a user of GSL and new to Guile, but I've
> tried to make some
progress in this direction with the scm_ interface. What
> I've done
rather closely follows the Guile manual and the available
> tutorials,
like Michael Gran's book ``How to extend C programs with
> Guile''.
Though it isn't much, I'd be happy to share what I have so
> far.
I really need to update or delete that doc. It is obsolete.
Unfortunately, there isn't really anything out there to
replace it.
-
Mike Gran
next prev parent reply other threads:[~2010-03-07 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 12:38 Guile and GSL Jason R. Green
2010-03-07 17:16 ` Ludovic Courtès
2010-03-07 18:50 ` Jason R. Green
2010-03-07 19:41 ` Mike Gran [this message]
2010-03-07 20:05 ` Jason R. Green
2010-03-10 15:21 ` Jason R. Green
2010-03-10 16:25 ` Ludovic Courtès
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=586212.40078.qm@web37907.mail.mud.yahoo.com \
--to=spk121@yahoo.com \
--cc=guile-devel@gnu.org \
--cc=jg525@cam.ac.uk \
/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).