From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: rm@tuxteam.de
Cc: guile-user@gnu.org
Subject: Re: common lisp compatability
Date: Wed, 27 Feb 2013 20:12:04 +0100 [thread overview]
Message-ID: <12168879.lZRVZPVguz@warperdoze> (raw)
In-Reply-To: <20130227195209.GA22684@seid-online.de>
On Wednesday, February 27, 2013 08:52:09 PM rm@tuxteam.de wrote:
> I find loop an invaluable syntactic extension for embedable scheme ...
> But I guess that's a matter of taste
Yes taste is differnt. To be onest the wow feeling of reading into
CL's loop macro facilities got me started becoming facinated with
lisps. So in a sense porting that was kind of closing the loop.
> Loop was one of the first things I included into my personal Denemo
> version (using the nice CL-Loop port by Heinrich Taube from his
> Common Music (v.2) - you do konw about that, do you?)
No i'm pretty ignorant about lot's of thingies. Anyway cool to know.
/Stefan
prev parent reply other threads:[~2013-02-27 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 16:21 common lisp compatability Stefan Israelsson Tampe
2013-02-27 19:52 ` rm
2013-02-27 19:12 ` Stefan Israelsson Tampe [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=12168879.lZRVZPVguz@warperdoze \
--to=stefan.itampe@gmail.com \
--cc=guile-user@gnu.org \
--cc=rm@tuxteam.de \
/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).