Differences between version #8185 and #8186

27c27
< One of the main differences between neko CFFI and C++ CFFI is how arrays are treated.
---
> One of the differences between neko CFFI and C++ CFFI is how arrays are treated. The neko implementation of arrays naturally allows it to provide and "value *" - pointer to series of elements.  However, this is only available on a C++ executable if the array is an array of Dynamic.  If the array is an array of Int, Bool or Double, then it may be possible to get an array of "double *" etc, which is a very efficient way of accessing the data (it is not possible to access stringl like this).  To write efficient code, your ndll should try the val_array_value function (if you are loaded in neko), then one or more of the specific array functions (eg, val_array_double if your haxe code takes an Array<Float>), before falling back to val_array_i if the other options are not available.
28a29,32
> ===== Byte Access =====
> 
> Neko uses "strings" as byte buffers, whereas C++ uses "Array of unsigned char", since its native string representation is an immutable string of wchar_t.  To access the data as a byte-buffer, you must first use "val_to_buffer" to convert the value handle to a buffer handle.  Using this, you can then call the various buffer manipulation functions.  The different type of handle ensures type checking at compile time.
>