Matthew,
I agree with John on this one.
In case you decide to release the files, you may want to correct
the comment in callback.rkt: it has (define b #f) and (define b null)
where I believe you mean (define b (box #f)) and (define b (box null)),
respectively. Also, among listed options for #:ke
> On Mar 14, 2018, at 6:22 PM, Matthew Flatt wrote:
>
>
Would it make sense to add these two examples to the documentation? Perhaps
just as links to github gists? Apologies if they’re already there; I took a
quick look and didn’t see them.
(I suggest this selfishly, because my ‘rsound’ pa
Matthew,
On 03/15/2018 04:22 AM, Matthew Flatt wrote:
At Wed, 14 Mar 2018 21:56:05 +0300, Dmitry Pavlov wrote:
I suspect that "my-callback" or something linked to it are moved
in memory by the garbage collector, and the pointer kept by
the C library is no longer valid. In the first simpler
case
At Wed, 14 Mar 2018 21:56:05 +0300, Dmitry Pavlov wrote:
> I suspect that "my-callback" or something linked to it are moved
> in memory by the garbage collector, and the pointer kept by
> the C library is no longer valid. In the first simpler
> case, that does not happen because it sets and uses th
Hello,
I am doing a Racket interface for a C library and the
garbage collector is my trouble again. I am asking for
advice from Racket FFI masters (actually, from anybody
who knows how to keep persistent callbacks from a C
side to Racket).
Earlier I was doing this:
(define _callback (_fun _int
5 matches
Mail list logo