Franck Reporter
	Description • 13 years ago

By default, the memory of an ArrayBuffer is initialized to zero (calloc_ in JSObject::allocateArrayBufferSlots).
It could be convenient to give embedders the ability to create uninitialized ArrayBuffers since data may be fill by the caller.

	David Mandelin [:dmandelin]
	Comment 1 • 13 years ago

(In reply to Franck from comment #0)
> By default, the memory of an ArrayBuffer is initialized to zero (calloc_ in
> JSObject::allocateArrayBufferSlots).
> It could be convenient to give embedders the ability to create uninitialized
> ArrayBuffers since data may be fill by the caller.

We're in the process of adding APIs to allow the caller to pass in an array, and that array gets used to hold the contents. Would that work for what you are trying to do?

	Franck Reporter
	Comment 2 • 13 years ago

Allowing embedders to give initialized array to construct an ArrayBuffer is a good feature, this could avoid the double initialization.
But the best scenario would be to give embedders the ability to construct an ArrayBuffer with data allocated by the embedding (like JL_NewUCString for strings) see also Bug 691446.

	David Mandelin [:dmandelin]
	Comment 3 • 13 years ago

OK, I'll try to work something like that into the transfer API work.