unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "B. Wilson via Guix-patches" via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 65934@debbugs.gnu.org
Subject: [bug#65934] [PATCH] gnu: Add smithforth.
Date: Thu, 05 Oct 2023 23:35:41 +0900	[thread overview]
Message-ID: <38GLEJ3MZ0JX3.2SNYY1FUB5OYX@wilsonb.com> (raw)
In-Reply-To: <87wmw16xtq.fsf@gnu.org>

Thanks for taking a look.

> Is this a binary VM image dump?
> 
> If so, is there source available, a way to bootstrap it?

The binary is the source, per se. The author hand-wrote x86_64 opcodes in hex,
which is what dmp.txt contains. This is "compiled" by using xxd to write those
bytes out to a file. Then system.fs is just a blob of Forth source that gets
appended to the binary.

It's kind of magical that this scheme works at all, but that's Forth for ya.

> Please use a gexp here for #:builder and instead of the (assoc-ref …)
> expressions above, use:
> 
>   #~(begin
>       ;; …
>       (let* ((sforth.dmp #$(package-source this-package))
>              (system.fs #$(origin …)))
>         …))
> 
> > +    (home-page "https://dacvs.neocities.org/SF/")
> > +    (synopsis "Forth programming language for x86-64 desktop computers")

Ah, nice. Thanks. Will do.

> Please add a ‘supported-systems’ field so the package is clearly marked
> as unsupported on architectures other than x86_64.

Perfect. I didn't realize we had such a field. Thanks!




  reply	other threads:[~2023-10-05 14:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14  5:27 [bug#65934] [PATCH] gnu: Add smithforth B. Wilson via Guix-patches via
2023-10-05 12:46 ` Ludovic Courtès
2023-10-05 14:35   ` B. Wilson via Guix-patches via [this message]
2023-10-05 15:01   ` B. Wilson via Guix-patches via
2023-10-08 21:38     ` bug#65934: " Ludovic Courtès

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=38GLEJ3MZ0JX3.2SNYY1FUB5OYX@wilsonb.com \
    --to=guix-patches@gnu.org \
    --cc=65934@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).