|
| From: | Tony Sidaway |
| Subject: | Re: [Chicken-users] Re: object-evict, string ports, safe-foreign-wrapper, foreign-primitive, Cheney on the Victoria Line, etc (was: What happens to a (non-simple) Scheme object sent to a foreign function?) |
| Date: | Mon, 5 Feb 2007 08:22:59 +0000 |
On 2/5/07, felix winkelmann <address@hidden> wrote:
sufficiently big). An alternative is to create a suitably sized byte-vector beforehand (in Scheme, using the heap) and copying the data inside a block of foreign code (or use "move-memory!").
Ah! I didn't know move-memory existed. This is probably exactly what I need. As you suggest I can create the type of object I need and just copy the raw data block into it, with the caveat that the byte order of data received from a remote source may not be as expected. No need to play "limbo" with the nursery.
| [Prev in Thread] | Current Thread | [Next in Thread] |