search for: copy_int_array

If you were thinking about writing a note for 3.8 but didn't get around to it yet, this is the final reminder. (In particular, the notes for X86 and PowerPC could use some attention.) Thanks, Hans On Thu, Feb 11, 2016 at 4:16 PM, Hans Wennborg <hans at chromium.org> wrote: > Dear lots of people, > > The first comments on the 3.7 release expressed surprise that there > were

...| RLenValue -> pr "int * value" | RLenTypeVal -> pr "hive_type * string" | RInt32 -> pr "int32" | RInt64 -> pr "int64" @@ -1685,6 +1693,7 @@ static hive_type HiveType_val (value); static value Val_hive_type (hive_type); static value copy_int_array (size_t *); static value copy_type_len (size_t, hive_type); +static value copy_len_value (size_t, hive_value_h); static value copy_type_value (const char *, size_t, hive_type); static void raise_error (const char *) Noreturn; static void raise_closed (const char *) Noreturn; @@ -1707,6 +1716,7...

...| RLenValue -> pr "value * int" | RLenTypeVal -> pr "hive_type * string" | RInt32 -> pr "int32" | RInt64 -> pr "int64" @@ -1685,6 +1693,7 @@ static hive_type HiveType_val (value); static value Val_hive_type (hive_type); static value copy_int_array (size_t *); static value copy_type_len (size_t, hive_type); +static value copy_len_value (size_t, hive_value_h); static value copy_type_value (const char *, size_t, hive_type); static void raise_error (const char *) Noreturn; static void raise_closed (const char *) Noreturn; @@ -1707,6 +1716,7...

On Windows, there exist at least two APIs for dealing with the Registry: The Win32 API (RegCreateKeyA, RegCreateKeyW, etc.) works with null-terminated ASCII or UTF-16 strings. The native API (ZwCreateKey, etc.), on the other hand works with UTF-16 strings that are stored as buffers+length and may contain null characters. Malware authors have been relying on the Win32 API's inability to

Dear lots of people, The first comments on the 3.7 release expressed surprise that there were no changes to the X86 or ARM targets. There had of course been a lot of hard work and many changes, but none of it was mentioned in the release notes. Please help make the release notes more comprehensive this time. The notes are of course not as important as the actual code, but they do get read, and