It would be nice to be able to use a TypedArray as a C array/pointer when performing a js-ctypes call. I believe it would be rather simple to adapt ImplicitConvert for that purpose.
Created attachment 621509 [details] [diff] [review] First prototype
Comment on attachment 621509 [details] [diff] [review] First prototype Hmm. I like everything here except that nothing is holding on to the TypedArray, so it would be easy for this pointer to be taken, implicitly, and then for the buffer to be GC'd, leaving a dangling ctypes pointer. One way around that is to move this code to ExplicitConvert. Another is to create utility functions: ctypes.bufferPtr(buffer or typedarray) ctypes.addressOfElement(typedarray, index) Another is to create a property on the pointer CData object that refers back to the TypedArray (but that's lame). Another possibility is to allow this conversion only if isArgument is true, similar to what we do for strings. For arguments, the conversion is safe at least for the duration of the C function call, since all arguments are rooted on the JS stack. Or we can leave it like it is and be really careful. It's up to you, you're the main ctypes user right now.
Actually, this is just the same thing we already do for js-ctypes arrays. It should be totally fine.
Comment on attachment 621509 [details] [diff] [review] First prototype no changes needed, post an updated patch for review One note, there are a few bits in here that seem to belong to a different patch: the change to dom/system/OSFileConstants.cpp, and the one to toolkit/components/osfile/osfile_unix_front.jsm.
Created attachment 624009 [details] [diff] [review] mplicitConvert ArrayBuffer to array or pointer Same patch, with a few more comments and without parasite code.
Comment on attachment 624009 [details] [diff] [review] mplicitConvert ArrayBuffer to array or pointer Review of attachment 624009 [details] [diff] [review]: ----------------------------------------------------------------- ::: toolkit/components/ctypes/tests/unit/test_jsctypes.js.in @@ +61,1 @@ > } Did you want these new print calls checked in? They don't hurt anything, afaik, so it's fine with me. @@ +1910,5 @@ > } > } > > function run_ArrayType_tests() { > + do_print("run_ArrayType_tests"); Here's another do_print(), just in case you meant to remove them. @@ +2051,5 @@ > + c.value = c_arraybuffer; > + } catch(x) { > + exn = x; > + } > + do_check_true(!!exn); Use do_check_throws.
Created attachment 625748 [details] [diff] [review] mplicitConvert ArrayBuffer to array or pointer
Created attachment 625956 [details] [diff] [review] ImplicitConvert ArrayBuffer to array or pointer
https://hg.mozilla.org/integration/mozilla-inbound/rev/9320ebf5821d
https://hg.mozilla.org/mozilla-central/rev/9320ebf5821d
*** Bug 710830 has been marked as a duplicate of this bug. ***
Title is actually a misnomer.
Documentation started here: https://developer.mozilla.org/en-US/docs/Mozilla/js-ctypes/Using_js-ctypes/Working_with_ArrayBuffers Probalby needs some serious technical review.
or
