From: Noah Lavine <noah.b.lavine@gmail.com>
To: Ian Price <ianprice90@googlemail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Programming racket like in guile
Date: Sat, 23 Feb 2013 10:39:36 -0500 [thread overview]
Message-ID: <CA+U71=MScTvqiqqhUyQZERaGv+qVX7q-iU8JeoFZQQAHqYy5MA@mail.gmail.com> (raw)
In-Reply-To: <87sj4nahfs.fsf@Kagami.home>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
Hello,
On Fri, Feb 22, 2013 at 9:32 PM, Ian Price <ianprice90@googlemail.com>wrote:
> Daniel Hartwig <mandyke@gmail.com> writes:
>
> > For those parts specific to racket, did you consider the (language
> > racket ..) namespace, where an eventual language definition could be
> > placed also?
>
> That sounds somewhat misleading, since Racket is not really one
> language. Yeah, there is #lang racket, but they have others as well.
>
It's true that racket is both a programming system for many languages and
the name of one specific language. I don't think it's too ambiguous to use
(language racket ...) for that one specific language. After all, if we
don't call it racket, then that language has no name!
Unless you want to use (language racket ...) for all of the things
supported by Racket, and maybe (language racket racket) for the actual
#lang racket language. It seems excessive to me, but I'm not completely
sure about that.
Best,
Noah
[-- Attachment #2: Type: text/html, Size: 1520 bytes --]
next prev parent reply other threads:[~2013-02-23 15:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 20:59 Programming racket like in guile stefan.itampe
2013-02-22 15:56 ` Ludovic Courtès
2013-02-22 19:04 ` stefan.itampe
2013-02-24 21:07 ` Ludovic Courtès
2013-02-24 21:47 ` Stefan Israelsson Tampe
2013-02-23 0:54 ` Daniel Hartwig
2013-02-23 2:32 ` Ian Price
2013-02-23 15:39 ` Noah Lavine [this message]
2013-02-23 16:28 ` Stefan Israelsson Tampe
2013-02-23 12:44 ` Stefan Israelsson Tampe
2013-02-23 15:36 ` Noah Lavine
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='CA+U71=MScTvqiqqhUyQZERaGv+qVX7q-iU8JeoFZQQAHqYy5MA@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--cc=guile-devel@gnu.org \
--cc=ianprice90@googlemail.com \
/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).