From: Catonano <catonano@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-user@gnu.org, Matt Wette <matt.wette@gmail.com>
Subject: Re: type friction C <-> scheme
Date: Sun, 11 Jun 2017 19:15:00 +0200 [thread overview]
Message-ID: <CAJ98PDwG5G2+PGv5quyq8c-VetoeBWDb_0tig9axU-XhB=uDiQ@mail.gmail.com> (raw)
In-Reply-To: <87d1ab3wfr.fsf@netris.org>
2017-06-11 7:50 GMT+02:00 Mark H Weaver <mhw@netris.org>:
> Catonano <catonano@gmail.com> writes:
>
> > 2017-06-10 0:33 GMT+02:00 Matt Wette <matt.wette@gmail.com>:
> >
> > 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.
>
Ok, there was a misunderstanding here
I thought that iin that context `*' was being exported from (system
foreign) too and it was bound to someting used to represent a C pointer
I hadn't understood that it is instead bound to the vanilla multiplication !
> > 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.
>
sure. Now I understand better
>
> 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.
>
Right, right
Thanks for your remarks
Mark, would you mind to take a look at the other thread (#define SOMETHING
some_value) ?
I'm stuck in wrapping this funtion from Freexl
Thanks again !
next prev parent reply other threads:[~2017-06-11 17:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 20:36 type friction C <-> scheme Catonano
2017-06-09 20:52 ` Mike Gran
2017-06-09 21:33 ` Catonano
2017-06-09 20:56 ` Matt Wette
2017-06-09 21:39 ` Catonano
2017-06-09 22:33 ` Matt Wette
2017-06-10 6:26 ` Catonano
2017-06-11 5:50 ` Mark H Weaver
2017-06-11 13:07 ` Matt Wette
2017-06-11 17:15 ` Catonano [this message]
2017-06-11 18:01 ` Matt Wette
2017-06-11 18:20 ` Catonano
2017-06-12 8:00 ` David Pirotte
2017-06-12 12:45 ` Matt Wette
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='CAJ98PDwG5G2+PGv5quyq8c-VetoeBWDb_0tig9axU-XhB=uDiQ@mail.gmail.com' \
--to=catonano@gmail.com \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
--cc=mhw@netris.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).