I'm not sure, but I think I can be content with passing Racket bytes across the
foreign interface boundary for the C runtime to use given the u8vector
equivalence. Only thing I'm not clear on: Is it a good idea for me to designate
the byte string as a _gcpointer on the "*" marked line, or does
On Sun, May 23, 2021 at 7:57 PM Matthew Flatt wrote:
> At Sun, 23 May 2021 14:57:42 +, Sage Gerard wrote:
> > Is there a cross-VM way to pass an arbitrary input port to the C
> > runtime (e.g. via open-input-bytes), such that the C runtime can read
> > bytes on its own?
>
> No, not unless
At Sun, 23 May 2021 14:57:42 +, Sage Gerard wrote:
> Is there a cross-VM way to pass an arbitrary input port to the C
> runtime (e.g. via open-input-bytes), such that the C runtime can read
> bytes on its own?
No, not unless you know that the port's implementation is sufficiently
constrained.
Hi all,
I have a C shared library exposing a simplified interface for computing message
digests. Here's a `while` that reads bytes using a callback.
https://github.com/zyrolasting/xiden/blob/libcrypto/crypto/crypto.c#L46
A compatible callback provided by Racket might look like this.
(λ (buf
4 matches
Mail list logo