From: Jean Abou Samra <jean@abou-samra.fr>
To: Walter Lewis <wklew@mailbox.org>, guile-user@gnu.org
Subject: Re: Breaking hygiene with syntax-rules?
Date: Sat, 12 Aug 2023 01:55:27 +0200 [thread overview]
Message-ID: <3b9c8777ca81c3d40e6df9d1e97ee12a59ead3d5.camel@abou-samra.fr> (raw)
In-Reply-To: <1f5c2e6b-5c04-7d56-18c1-276bc7b36a01@mailbox.org>
[-- Attachment #1: Type: text/plain, Size: 2209 bytes --]
Le vendredi 11 août 2023 à 18:50 -0400, Walter Lewis via General Guile related discussions a écrit :
> Sorry I typed that code offhand and it had some mistakes; should be:
>
> ```
> (use-modules (srfi srfi-9) (system foreign))
>
> (define-syntax define-ffi-wrapper
> (syntax-rules ()
> ((_ size
> name wrap unwrap predicate
> to-pointer from-pointer)
> (begin
> (define-record-type name
> (wrap bv pointer)
> predicate
> (bv unwrap)
> (pointer pointer-ref pointer-set!))
> (define (to-pointer x)
> (or (pointer-ref x)
> (let ((pointer (bytevector->pointer x)))
> (pointer-set! x pointer)
> pointer)))
> (define (from-pointer pointer)
> (wrap (pointer->bytevector pointer size)
> pointer))))))
> ```
You could just turn that into a syntax-case macro, use gensym to generate the names, and insert them using with-syntax or quasisyntax. For example (untested):
```
(use-modules (srfi srfi-9) (system foreign))
(define-syntax define-ffi-wrapper
(lambda (sintax)
(syntax-case sintax ()
((_ size
name wrap unwrap predicate
to-pointer from-pointer)
(with-syntax ((pointer-ref (datum->syntax sintax (gensym "pointer-ref")))
(pointer-set! (datum->syntax sintax (gensym "pointer-set!"))))
#'(begin
(define-record-type name
(wrap bv pointer)
predicate
(bv unwrap)
(pointer pointer-ref pointer-set!))
(define (to-pointer x)
(or (pointer-ref x)
(let ((pointer (bytevector->pointer x)))
(pointer-set! x pointer)
pointer)))
(define (from-pointer pointer)
(wrap (pointer->bytevector pointer size)
pointer))))))))
```
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-08-11 23:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 2:35 Breaking hygiene with syntax-rules? Walter Lewis via General Guile related discussions
2023-08-11 5:07 ` Dr. Arne Babenhauserheide
2023-08-11 8:00 ` Jean Abou Samra
2023-08-11 8:33 ` Dr. Arne Babenhauserheide
2023-08-11 23:57 ` Jean Abou Samra
2023-08-12 5:57 ` Dr. Arne Babenhauserheide
2023-08-11 13:34 ` Walter Lewis via General Guile related discussions
2023-08-11 22:50 ` Walter Lewis via General Guile related discussions
2023-08-11 23:55 ` Jean Abou Samra [this message]
2023-08-11 23:57 ` Jean Abou Samra
2023-08-12 0:19 ` Walter Lewis
2023-08-12 0:58 ` Jean Abou Samra
2023-08-12 5:59 ` Dr. Arne Babenhauserheide
2023-08-14 19:26 ` Thompson, David
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=3b9c8777ca81c3d40e6df9d1e97ee12a59ead3d5.camel@abou-samra.fr \
--to=jean@abou-samra.fr \
--cc=guile-user@gnu.org \
--cc=wklew@mailbox.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.
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).