guile-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: type friction C <-> scheme


From: Matt Wette
Subject: Re: type friction C <-> scheme
Date: Sun, 11 Jun 2017 06:07:14 -0700

> On Jun 10, 2017, at 10:50 PM, Mark H Weaver <address@hidden> wrote:
> 
> Catonano <address@hidden <mailto:address@hidden>> writes:
> 
>> 2017-06-10 0:33 GMT+02:00 Matt Wette <address@hidden>:
>> 
>> I think Mike caught your real error: you were passing (list ‘* ‘int ‘*) and
>>> it wants (list ‘* int ‘*).  `int’ is a variable defined by guile.
>>> 
>> 
>> And isn't `*' a variable defined in guile too ?
>> 
>> 
>>> 
>>> scheme@(guile-user)> (use-modules (system foreign))
>>> scheme@(guile-user)> int
>>> $1 = 8
>>> 
>> 
>> yes, and
>> 
>> scheme@(freexl common)> *
>> $14 = #<procedure * (#:optional _ _ . _)>
> 
> 'int' is a variable exported by (system foreign) whose sole purpose is
> to represent a foreign type.
> 
> '*' is something completely different, namely a procedure to multiply
> numbers.  IMO, it would be a nasty hack for the FFI to check
> specifically for a multiplication procedure and interpret that as a
> pointer type.
> 
>> I took a look at the guile-gcrypt code again
>> 
>> it's full of things like
>> 
>> '(* * ,int ,size_t *)
>> 
>> that is, only asterisks (pointers) are quoted
>> 
>> Other types are not
>> 
>> So this must be an established convention
>> 
>> It just seems unconsistent to me
> 
> I agree that it's inconsistent, but '* is shorter than any descriptive
> variable name that we might have chosen for this purpose, and pointers
> are common enough to warrant a short name.
> 
> On the other hand, if we had used symbols uniformly for all foreign
> types, then it would have been impossible to bind your own type names
> (e.g. for struct types) without adding a global registry of foreign
> types, which would have various nasty problems such as the potential for
> collisions between unrelated libraries.
> 
>     Regards,
>       Mark


Yes.  In the ffi-helper I’m working on, which is intended to help auto-generate 
ffi code from C headers, I use #:prefix to avoid clashes: 

(define-module (cairo cairo)
  #:use-module (ffi-help)
  #:use-module ((system foreign) #:prefix ffi:)
  #:use-module ((bytestructures guile) #:prefix bs:)
  )
(define bs:struct bs:bs:struct)
…
;; cairo_matrix_t
(define cairo_matrix_t
  (bs:struct
    (list `(xx ,bs:double)
          `(yx ,bs:double)
          `(xy ,bs:double)
          `(yy ,bs:double)
          `(x0 ,bs:double)
          `(y0 ,bs:double))))
(export cairo_matrix_t)
…
;; void cairo_line_to(cairo_t *cr, double x, double y);
(define cairo_line_to
  (let ((f (ffi:pointer->procedure
             ffi:void
             (lib-func "cairo_line_to")
             (list '* ffi:double ffi:double))))
    (lambda (cr x y)
      (let ((~cr ((unwrap-cairo_t* cr)))) (f ~cr x y)))))
(export cairo_line_to)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]