From: Catonano <catonano@gmail.com>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: #define SOMETHING some_value
Date: Sun, 11 Jun 2017 19:08:11 +0200 [thread overview]
Message-ID: <CAJ98PDyvRduG33ecs2gr3f18nZ1Meumq4zy0eSGRF0yQy_H50A@mail.gmail.com> (raw)
In-Reply-To: <BC023AF1-5BF3-4432-A8D0-DCADF2F0503E@gmail.com>
2017-06-10 17:55 GMT+02:00 Matt Wette <matt.wette@gmail.com>:
>
>
>
Yea. I may have steered you wrong before. (I didn’t look back.) The
> argument signature might need to be (list ‘* unsigned-short ‘*) rather than
> your current one with unsigned-int.
>
I tried with no result :-/
Also, unsigned-short isn't mentioned in the guile manual
(API reference -> Foreign pointers -> Foreign types)
next prev parent reply other threads:[~2017-06-11 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-10 8:31 #define SOMETHING some_value Catonano
2017-06-10 9:51 ` Amirouche Boubekki
2017-06-11 19:42 ` Mark H Weaver
2017-06-11 20:07 ` Matt Wette
2017-06-15 19:21 ` Matt Wette
2017-06-16 16:37 ` Catonano
2017-06-10 15:55 ` Matt Wette
2017-06-11 17:08 ` Catonano [this message]
2017-06-11 20:06 ` Mark H Weaver
2017-06-11 20:32 ` Catonano
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=CAJ98PDyvRduG33ecs2gr3f18nZ1Meumq4zy0eSGRF0yQy_H50A@mail.gmail.com \
--to=catonano@gmail.com \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
/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).