[PATCH 3/6] ncrypt: Implement NCryptCreatePersistedKey.

[Santino Mazza]

El jue, 3 mar 2022 a la(s) 17:16, Santino Mazza (mazzasantino1206 at gmail.com)
escribió:

>
> El mié, 2 mar 2022 a la(s) 06:28, Hans Leidekker (hans at codeweavers.com)
> escribió:
>
>>
>> Why do you need to store the provider handle here? Note that's it's also
>> set as a key property.
>>
>>  For internal usage it's going to be more straightforward (and fast? I
> don't think it's going to make a big difference) to have it saved on a
> struct member. But I admit it looks a little repetitive and that it could
> get out of control at some point (by having to  take into consideration the
> struct member and also the property at the same time), I was thinking into
> making the struct member a pointer to the value of the property, but
> nothing guarantees that the memory address of the properties addresses will
> stay the same when adding new properties. Do you have some suggestions? For
> now I will just remove the struct member and use properties.
>
 I messed up the last phrase. I meant that nothing guarantees that the
address of the properties array will stay the same when adding a new
property.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20220303/63f334cf/attachment.htm>