From: "Bill Schottstaedt" <bil@ccrma.Stanford.EDU>
To: "Kjetil S. Matheussen" <k.s.matheussen@notam02.no>,
Cmdist@ccrma.Stanford.EDU, guile-devel@gnu.org
Subject: Re: [CM] Extending Snd with Eval-C and Snd-Rt
Date: Thu, 10 Jan 2008 15:56:40 -0800 [thread overview]
Message-ID: <20080110234927.M172@ccrma.Stanford.EDU> (raw)
In-Reply-To: <Pine.LNX.4.64.0801110021400.8406@ttleush>
> This is my paper for the linux audio conference 2008:
Very interesting! Can we include it in the Snd tarball?
I wonder what the history of Guile was -- I had not associated
it with Jaffer, but with Tom Lord. I'll have to look again at
rscheme, if it would be a better choice.
next prev parent reply other threads:[~2008-01-10 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 23:29 Extending Snd with Eval-C and Snd-Rt Kjetil S. Matheussen
2008-01-10 23:56 ` Bill Schottstaedt [this message]
2008-01-11 0:40 ` [CM] " Kjetil S. Matheussen
2008-01-11 15:36 ` Andy Wingo
2008-01-13 0:46 ` Kjetil S. Matheussen
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=20080110234927.M172@ccrma.Stanford.EDU \
--to=bil@ccrma.stanford.edu \
--cc=Cmdist@ccrma.Stanford.EDU \
--cc=guile-devel@gnu.org \
--cc=k.s.matheussen@notam02.no \
/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).