>> Response
>>
>> *lpcbClass bytes optional  LPWSTR lpClass
>> 4 bytes optional data LPDWORD lpcbClass,
>> ignoring LPDWORD lpReserved,
>> 4 bytes optional LPDWORD lpcSubKeys,
>> 4 bytes optional LPDWORD lpcbMaxSubKeyLen,
>> 4 bytes optional LPDWORD lpcbMaxClassLen,
>> 4 bytes optional LPDWORD lpcValues,
>> 4 bytes optional LPDWORD lpcbMaxValueNameLen,
>> 4 bytes optional LPDWORD lpcbMaxValueLen,
>> 4 bytes optional LPDWORD lpcbSecurityDescriptor,
>> 8 bytes optional PFILETIME lpftLastWriteTime
>>
>
> Had to take out the aforementioned read of last_error. Also had to swap
> lpClass and lpcbClass, ie read the size first, perfectly logical but
> breaks the parameter passing order, bizarre. Do you think when M$
> assigns these things for someone to spec, it explicitly states "make it
> as awkward as possible".

I'll double-check this when I'm at my Windows machine again.

\David


-------------------------------------------------------------------------
SF.Net email is sponsored by: 
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel

Reply via email to