[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: type friction C <-> scheme
From: |
Catonano |
Subject: |
Re: type friction C <-> scheme |
Date: |
Fri, 9 Jun 2017 23:39:34 +0200 |
2017-06-09 22:56 GMT+02:00 Matt Wette <address@hidden>:
>
>
I think your outcome-ptr should be (bytevector->pointer (make-bytevector
> (sizeof unsigned-int)))
Thank you, Matt
The reason why I wrote it that way is because the previous function
(freexl_open) takes a pointer (a handler) and then more or less arbitrarily
allocates stuff onto it
The handler is meant to be passed as an argument to subsequent calls to the
other funtiions of the library
So I tought that the same would have happened with this outcome thing
Maybe I'm wrong
I'll think about this tomorrow, too
Thank you very much for your suggestion !
- type friction C <-> scheme, Catonano, 2017/06/09
- Re: type friction C <-> scheme, Mike Gran, 2017/06/09
- Re: type friction C <-> scheme, Matt Wette, 2017/06/09
- Re: type friction C <-> scheme,
Catonano <=
- Re: type friction C <-> scheme, Matt Wette, 2017/06/09
- Re: type friction C <-> scheme, Catonano, 2017/06/10
- Re: type friction C <-> scheme, Mark H Weaver, 2017/06/11
- Re: type friction C <-> scheme, Matt Wette, 2017/06/11
- Re: type friction C <-> scheme, Catonano, 2017/06/11
Re: type friction C <-> scheme, Matt Wette, 2017/06/11