From: "Marijn Schouten (hkBst)" <hkBst@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] *DEVELOPMENT* mail list, right?
Date: Fri, 08 Jun 2007 13:26:01 +0200 [thread overview]
Message-ID: <46693CC9.2050804@gentoo.org> (raw)
In-Reply-To: <20070405230345.GA22227@paradox.datanode.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi list,
I'd like to inform you about goings on in Scheme territory.
BEGIN INTERMEZZO
For those who've never heard of Scheme: Scheme is a modern minimal Lisp
programming language.
For those who ask themselves why on Earth people want to put up with Lots of
Irritating and Superfluous Parentheses:
A very enjoyable and insightful and, most importantly, ACCESSIBLE article
giving some insight in the power of program-data equivalence is at [
http://www.defmacro.org/ramblings/lisp.html ].
END OF INTERMEZZO
There are about a dozen Scheme implementations in the tree, all with their own
idiosyncratic way of doing things. For example the current Scheme standard
specifies a macro system, but in a lot of implementations you have to enable
it explicitly, and standard extensions (socalled SRFIs) have to be activated
differently for different implementation. All this makes it difficult to write
programs that work in all these implementations.
I want to avoid using just a single implementation, since I feel a
responsibillity to have a basic familiarity with all implementations that I
maintain (and a few that others maintain :) ). I have a few scripts to run
Scheme programs in multiple implementations that also double as my knowledge
base for bending different implementations to my will.
In the last few days I've added a new weapon to my arsenal. That weapon is
slib the portable Scheme library. It has been in the tree for a long time, but
it only used to support guile. Since yesterday slib-3.1.4-r3 supports six
implementations: bigloo drscheme elk gambit guile scm. To my knowledge, which
admittedly is a bit limited, Gentoo is the only distro that has this. At least
I'm pretty sure that Debian doesn't have it :) .
At the moment the script installed by slib to start an implementation with
slib loaded still doesn't work flawlessly in each case, so manually loading
slib is still preferred. I intend to fix it up later and possibly extend
support of slib to other implementations.
I always enjoy hearing from users. If you have a question about how to
activate macros or slib for a specific implementation or any other Scheme
question, please catch me in #gentoo-lisp. I really need to document all this
stuff some time, but things are still very much in motion right now and I
haven't decided how best to insulate users from these issues.
One more thing. Both the Scheme herd and the Common Lisp herd are currently
severely understaffed with one member each (not the same ;) ). If you are
interested in Lisp and want to help, come talk to me,
thoroughly enjoying basking in the power of Scheme, Gentoo and the Sun,
Marijn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGaTzJp/VmCx0OL2wRArn2AJ9hHK7O3aEsz1xFddOHLzDh27+tOwCeIDik
b9oROA0KffRcJkwSwrspKlw=
=fiPQ
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-06-08 11:27 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 23:03 [gentoo-dev] *DEVELOPMENT* mail list, right? Michael Cummings
2007-04-05 23:25 ` Joshua Jackson
2007-04-06 16:45 ` Ned Ludd
2007-04-06 19:49 ` Chris Gianelloni
2007-04-07 18:16 ` George Prowse
2007-04-08 13:23 ` Chris Gianelloni
2007-04-06 17:07 ` Alec Warner
2007-04-06 18:54 ` Doug Goldstein
2007-04-08 0:20 ` mail
2007-04-08 1:16 ` Steev Klimaszewski
2007-04-08 1:43 ` mail
2007-04-09 12:24 ` [gentoo-dev] hal-0.5.9 (was: *DEVELOPMENT* mail list, right?) Elias Probst
2007-04-06 19:57 ` [gentoo-dev] *DEVELOPMENT* mail list, right? Roy Marples
2007-04-06 20:57 ` [gentoo-dev] resolvconf Donnie Berkholz
2007-04-08 13:31 ` Roy Marples
2007-04-07 1:09 ` [gentoo-dev] Re: *DEVELOPMENT* mail list, right? Duncan
2007-04-06 20:19 ` Ryan Hill
2007-04-06 21:14 ` [gentoo-dev] " Rémi Cardona
2007-04-06 21:24 ` Petteri Räty
2007-04-08 13:53 ` Rémi Cardona
2007-04-06 21:38 ` [Off-topic] " Steven De Bock
2007-04-08 13:19 ` Chris Gianelloni
2007-04-08 19:26 ` William L. Thomson Jr.
2007-04-06 21:23 ` [gentoo-dev] " Christian Faulhammer
2007-04-07 2:24 ` [gentoo-dev] " Luca Barbato
2007-04-08 10:58 ` Jeffrey Gardner
2007-04-08 21:14 ` Roy Wright
2007-04-08 21:20 ` Christopher Sawtell
2007-04-08 23:30 ` William L. Thomson Jr.
2007-04-09 4:54 ` Jeffrey Gardner
2007-04-09 18:24 ` Roy Wright
2007-04-08 14:52 ` Raúl Porcel
2007-04-08 15:12 ` Joseph Jezak
2007-04-08 17:53 ` Tobias Scherbaum
2007-04-08 15:31 ` Paul Varner
2007-04-08 16:20 ` Josh Saddler
2007-04-09 14:15 ` Mike Kelly
2007-04-09 16:49 ` Donnie Berkholz
2007-04-11 6:40 ` Robin H. Johnson
2007-04-11 18:19 ` Donnie Berkholz
2007-04-11 20:40 ` Robin H. Johnson
2007-06-08 11:26 ` Marijn Schouten (hkBst) [this message]
2007-06-08 11:48 ` Raúl Porcel
2007-06-09 1:05 ` Michael Cummings
2007-06-09 9:51 ` Petteri Räty
2007-06-11 21:26 ` Bernard Cafarelli
2007-06-11 22:40 ` Rémi Cardona
-- strict thread matches above, loose matches on Subject: below --
2007-04-08 14:16 Brent Baude
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46693CC9.2050804@gentoo.org \
--to=hkbst@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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