>> I also found out the
>> hard wasy the UTF16 strings need to be terminated with
>> a double nul (0x0000).
Not to doubt you (I don't do anything in UTF-16), but can you show an
example of this?
I would have thought a single NULL character is enough.
The 1st byte of a Unicode character determines whether or not it's ascii or
not and I wouldn't think when encountering the first null, any reasonable
utf-16 interpretation would consume more than just that 1st byte.
On Sat, Jan 18, 2020 at 10:14 PM ToddAndMargo via perl6-users <
perl6-us...@perl.org> wrote:
> On 2020-01-18 04:55, Tobias Boege wrote:
> > BUT the terminating NUL character is not inserted by NativeCall and it
> > isn't inserted by &encode.
>
>
> Hi Tobias,
>
> I found this out the hard way. I also found out the
> hard wasy the UTF16 strings need to be terminated with
> a double nul (0x0000).
>
> -T
>
--
__________________
:(){ :|:& };:
