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: #define SOMETHING some_value
Date: Sun, 11 Jun 2017 22:32:16 +0200 [thread overview]
Message-ID: <CAJ98PDwRxmaD0Z2hBmFOpmYO5oz3q2ZVn_eKWGaF8mq9HvF15Q@mail.gmail.com> (raw)
In-Reply-To: <87o9tu2ssb.fsf@netris.org>
2017-06-11 22:06 GMT+02:00 Mark H Weaver <mhw@netris.org>:
> Catonano <catonano@gmail.com> writes:
>
> > 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 agree with Matt that you should use 'unsigned-short' here, since
> that's the type specified in the C function prototype. Although it is
> true that most platform ABIs will treat them equivalently for purposes
> of argument passing, the C standards provide no guarantee of that as far
> as I can tell.
>
yes, I corrected that to an unsigned-short
>
> > I tried with no result :-/
>
> What does "no result" mean here? For now, I will assume it means that
> you get the same error as before:
>
yes, I meant I was gettiing te same error as before
>
> ERROR: Throw to key `get-info-error' with args `(error-code -3)'.
>
> The -3 corresponds to:
>
> #define FREEXL_INVALID_HANDLE -3 /* Invalid xls_handle argument. */
>
Right, I found that out a few minutes ago
>
> So I would consider it likely that the problem is with the first
> argument (the handle), not the second one (the unsigned short).
>
Spot on !
I was assuming that the error returned was FREEXL_INVALID_INFO_ARG
I was wrong, of course.
I realized this just a ffew minutes ago !
Sorry for the noiise :-/
Thanks Mark !
prev parent reply other threads:[~2017-06-11 20:32 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
2017-06-11 20:06 ` Mark H Weaver
2017-06-11 20:32 ` Catonano [this message]
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=CAJ98PDwRxmaD0Z2hBmFOpmYO5oz3q2ZVn_eKWGaF8mq9HvF15Q@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).