From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: bug-guile@gnu.org
Subject: Re: guile can't find dynamically loaded library
Date: 09 Oct 2002 00:40:28 +0200 [thread overview]
Message-ID: <87wuostuzn.fsf@zagadka.ping.de> (raw)
In-Reply-To: <200210082142.g98Lgr513781@orchestra.cs.caltech.edu>
Michael Vanier <mvanier@cs.caltech.edu> writes:
> I'm pretty happy to see guile catching up with other scripting languages.
> I'm especially happy with how easy it is to write extensions; I don't know
> of any other scripting language that has such a trivially simple extension
> mechanism.
I'm very happy to hear this!
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2002-10-08 22:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 1:08 guile can't find dynamically loaded library Michael Vanier
2002-10-03 18:34 ` Marius Vollmer
2002-10-05 6:05 ` Michael Vanier
2002-10-05 18:35 ` Paul Jarc
2002-10-08 21:30 ` Marius Vollmer
2002-10-08 21:42 ` Michael Vanier
2002-10-08 22:40 ` Marius Vollmer [this message]
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=87wuostuzn.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=bug-guile@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).