From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: λ the ultimate showcase
Date: Thu, 10 Sep 2009 23:46:55 +0200 [thread overview]
Message-ID: <87bplio4kw.fsf@gnu.org> (raw)
In-Reply-To: 877hw638iu.fsf@arudy.ossau.uklinux.net
Neil Jerram <neil@ossau.uklinux.net> writes:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Hey,
>>
>> Now that we have Unicode, let’s not put it to good use!
>>
>> (define-syntax λ
>> (syntax-rules ()
>> ((_ formals body ...)
>> (lambda formals body ...))))
>
> Can it be overridden?
Yes. In the end it boils down to ‘module-define!’.
> Just in case someone writes an algorithm where they'd really like to
> have λ as a variable?
One can always use ‘λ’ or ‘lambda’ as a local variable name:
(let ((λ 2))
(+ λ 3))
> If the answer to the above is Yes, definitely.
Cool, let’s do it! :-)
(Then we’ll want “’” for ‘quote’, “‘” for ‘quasiquote’, etc. etc.)
Thanks,
Ludo’.
prev parent reply other threads:[~2009-09-10 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 15:40 λ the ultimate showcase Ludovic Courtès
2009-09-10 17:37 ` Ludovic Courtès
2009-09-10 19:27 ` Neil Jerram
2009-09-10 21:46 ` Ludovic Courtès [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=87bplio4kw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).