From: dskr <dskr@mac.com>
To: guile-user@gnu.org
Subject: more spam on extension language fu
Date: Wed, 5 Dec 2007 15:04:52 -0500 [thread overview]
Message-ID: <0BDB53DA-6AE5-43D3-996B-1BDBC7A0F94D@mac.com> (raw)
Hi,
One of the things I value most about Guile as an extension language is
the terrific set of facilities for introspection available. I've
always thought the included readline support was vile (mostly due to
readline itself) and so
I've been using my own pure-guile completion library for about 7 years.
=> (tab-complete-string "(socke" (current-module))
"(socket"
=> (tab-complete-string "(socket " (current-module))
"(socket family"
=> (tab-complete-string "(socket AF_IN" (current-module))
"(socket AF_INET"
=> (tab-complete-string "(socket AF_INET SOCK_ST" (current-module))
"(socket AF_INET SOCK_STREAM"
The big plus for me is that it has let me build GTK and AJAX
interfaces that get the benefit of completions
without the C-fu and fport orientation of the readline stuff. The fact
that this facility can be built in Scheme is a testament to Guile.
What's the point? The point is that Guile is my extension language and
also my interface for navigating my own sprawling code. I'm concerned
that many of the changes that would push Guile down the performance
path also impact the terrific and underused introspection features
that Guile already has.
Tab completion is a parlor trick. The fact that environments are
inspectable and that procedure source is recoverable mean that many
powerful lexical analysis tricks are easier in Guile than in many
other Scheme environments.
Cheers,
Dan Ridge
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2007-12-05 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 20:04 dskr [this message]
2007-12-12 22:03 ` more spam on extension language fu 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=0BDB53DA-6AE5-43D3-996B-1BDBC7A0F94D@mac.com \
--to=dskr@mac.com \
--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).