From: Philip McGrath <philip@philipmcgrath.com>
To: Jack Hill <jackhill@jackhill.us>
Cc: 48308@debbugs.gnu.org
Subject: [bug#48308] [PATCH] gnu: racket: Update to 8.1.
Date: Sun, 9 May 2021 17:06:43 -0400 [thread overview]
Message-ID: <f4914fac-f493-2f08-6f15-e99ba1f37e0a@philipmcgrath.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2105091630040.2109@marsh.hcoop.net>
On 5/9/21 4:34 PM, Jack Hill wrote:
> Not related to the update, but I noticed `guix lint` complain about the
> racket synopsis (it begins with an article). I think we could just drop
> the 'a' and leave the rest of it as is and it would still make sense and
> satisfy the linter.
Ah, yes, I had noticed that. It's not a big deal and I'm happy to defer
to community consensus. I had kept the "a" because it's a reference to
Felleisen et. al.'s "A Programmable Programming Language"
(Communications of the ACM, March 2018) [1], the title of which in turn
is a quote Foderaro's "LISP: Introduction" (Communications of the ACM,
September 1991) [2]:
> When Lisp adopts a new paradigm, it not only replicates
> existing practice, but goes beyond it to become a testbed
> for advancing the state of the art. Why has Lisp been able
> to adapt so easily when other languages have not? One
> reason is that Lisp is a *programmable* programming language.
> Not only can you program *in* Lisp (that makes it a programming
> language) but you can program the language itself.
[1]:
https://cacm.acm.org/magazines/2018/3/225475-a-programmable-programming-language/fulltext
[2]: https://doi.org/10.1145/114669.114670
-Philip
next prev parent reply other threads:[~2021-05-09 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 7:28 [bug#48308] [PATCH] gnu: racket: Update to 8.1 Philip McGrath
2021-05-09 20:34 ` Jack Hill
2021-05-09 21:06 ` Philip McGrath [this message]
2021-05-10 13:13 ` bug#48308: " Efraim Flashner
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=f4914fac-f493-2f08-6f15-e99ba1f37e0a@philipmcgrath.com \
--to=philip@philipmcgrath.com \
--cc=48308@debbugs.gnu.org \
--cc=jackhill@jackhill.us \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.