all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: FYI: guile-scheme bindings to GNU Mach and the Hurd
Date: Tue, 04 May 2021 22:18:03 +0200	[thread overview]
Message-ID: <1ba5e5147ae377d0e301863f8e794fe5b92b6a04.camel@telenet.be> (raw)
In-Reply-To: <87r1io5076.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]

Ludovic Courtès schreef op zo 02-05-2021 om 22:51 [+0200]:
> > [...] moved it to <https://notabug.org/guile-hurd/guile-hurd>;.
> 
> Nice!  I knew of the Common Lisp effort this is based on, and the idea
> of reusing the .lisp code unchanged is smart.  Looks promising!

The initial idea was to keep most of the .lisp code unchanged and ‘convert’
most lisp -> Scheme by defining appropriate macro's. However:

 * the procedure names are adapted to Scheme conventions
   (! for imperative procedures, ? instead of -p for predicates, ...)

 * the Lisp code is rather sparsely documented, so I'm adding docstrings
   and some comments. Particularily important for people who don't know much
   about how the Hurd and Mach works (e.g. me (-:)).

 * the Lisp code uses <https://www.common-lisp.net/project/cffi/>
   as foreign function interface, which uses CLOS.  While much of CLOS
   can be ‘implemented’ with macros that use GOOPS, there are some incompatibilities
   (e.g., :after, :before and something else I forgot do not exist in GOOPS)
   which cannot be easily worked around

   It is (in-progress) fairly easy to modify the mach/*.lisp code to use guile's
   FFI instead.  E.g., see

   <https://notabug.org/guile-hurd/guile-hurd/src/cafd4a0e3b679bef14ff8327773c00221d5c0981/mach/port-move.scm>

  and

  <https://notabug.org/guile-hurd/guile-hurd/src/cafd4a0e3b679bef14ff8327773c00221d5c0981/mach/ffi.scm>

I probably need to change the README.org.

There were some other points I wished to raise, but I'll stop here so
you don't have to wait a week on my response.

Greetings,
Maxime.



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2021-05-04 20:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01 15:04 FYI: guile-scheme bindings to GNU Mach and the Hurd Joshua Branson
2021-05-01 19:48 ` Maxime Devos
2021-05-02  6:03   ` Mark H Weaver
2021-05-02 20:51   ` Ludovic Courtès
2021-05-04 20:18     ` Maxime Devos [this message]
2021-05-06 16:30       ` Ludovic Courtès
2021-05-06 20:58         ` Maxime Devos
2021-05-11 20:29           ` 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

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

  git send-email \
    --in-reply-to=1ba5e5147ae377d0e301863f8e794fe5b92b6a04.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=guix-devel@gnu.org \
    --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.