From: "B. Wilson via Guix-patches" via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 65935@debbugs.gnu.org
Subject: [bug#65935] [PATCH] gnu: Add ngn-k.
Date: Mon, 20 Nov 2023 20:52:04 +0900 [thread overview]
Message-ID: <2JTFTAZZGPVJ8.2RLE458OBECS0@wilsonb.com> (raw)
In-Reply-To: <877cmcr7d3.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> wrote:
> … I find it hard to believe they’re “readable” to anyone in the sense of
> being the “preferred form” for modifications or even just studying it.
> (Heck, even the Makefile has optional whitespace removed, as if trying
> hard to make it unreadable!)
It's definitely a gawker at first sight. For comparison, take a look at this in
progress YAML parser of mine:
https://github.com/xelxebar/dayaml/blob/22d20b335bfc99e8e140fee8ca5e7f5f1320f72d/Y.apln
I swear that I sweat blood on this making it as brutally direct and clear as
possible!
> I don’t think we have a precedent here; I wouldn’t want to make a
> decision based on a personal judgment, and I understand I know nothing
> about the APL language family, but someone will have to clarify how
> those 1.2K lines of C were written/generated.
From indirectly knowing the dev, my understanding is that the code is
hand-written. The motivation is basically to decrease the cognitive dissonance
between writing K and writing C. Ideally, you'd want to just write a K
interpreter using K, but that's a whole different can of worms.
The de facto K interpreter, Shakti, is proprietary and expensive, but from
talking to some people on the inside, I gather that it's also written in this
extremely terse style.
> I’d love to hear what others think!
>
> Thanks,
> Ludo’.
Anyway, thanks for reviving this.
prev parent reply other threads:[~2023-11-20 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 5:39 [bug#65935] [PATCH] gnu: Add ngn-k B. Wilson via Guix-patches via
2023-10-18 20:49 ` Ludovic Courtès
2023-10-20 15:06 ` B. Wilson via Guix-patches via
2023-11-20 11:28 ` Ludovic Courtès
2023-11-20 11:52 ` B. Wilson via Guix-patches via [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2JTFTAZZGPVJ8.2RLE458OBECS0@wilsonb.com \
--to=guix-patches@gnu.org \
--cc=65935@debbugs.gnu.org \
--cc=elaexuotee@wilsonb.com \
--cc=ludo@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.
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.