On Wed, 13 Jul 2022 16:40:48 GMT, Valerie Peng wrote:
>>> pkcs11.h is a standard header file from OASIS. Best to leave it alone. Just
>>> my .02.
>>
>> The only change to pkcs11.h is in a comment though, the other changes are
>> outside the ANSI C headers from the standard. Should I just rever
On Thu, 14 Jul 2022 02:48:07 GMT, Julian Waters wrote:
>> Several instances of function pointers in jdk.crypto.cryptoki are marked
>> with the dllimport attribute, which should only be applied to symbol
>> declarations, of which a typedef'd function pointer is not. This would only
>> be useful
> Several instances of function pointers in jdk.crypto.cryptoki are marked with
> the dllimport attribute, which should only be applied to symbol declarations,
> of which a typedef'd function pointer is not. This would only be useful if a
> function pointer defined in the linked dll is desired t
> Several instances of function pointers in jdk.crypto.cryptoki are marked with
> the dllimport attribute, which should only be applied to symbol declarations,
> of which a typedef'd function pointer is not. This would only be useful if a
> function pointer defined in the linked dll is desired t
On Wed, 13 Jul 2022 16:40:48 GMT, Valerie Peng wrote:
> > > pkcs11.h is a standard header file from OASIS. Best to leave it alone.
> > > Just my .02.
> >
> >
> > The only change to pkcs11.h is in a comment though, the other changes are
> > outside the ANSI C headers from the standard. Should
On Sat, 9 Jul 2022 06:05:09 GMT, Julian Waters wrote:
> > pkcs11.h is a standard header file from OASIS. Best to leave it alone. Just
> > my .02.
>
> The only change to pkcs11.h is in a comment though, the other changes are
> outside the ANSI C headers from the standard. Should I just revert t
On Sat, 9 Jul 2022 07:46:39 GMT, Julian Waters wrote:
>> Several instances of function pointers in jdk.crypto.cryptoki are marked
>> with the dllimport attribute, which should only be applied to symbol
>> declarations, of which a typedef'd function pointer is not. This would only
>> be useful
> Several instances of function pointers in jdk.crypto.cryptoki are marked with
> the dllimport attribute, which should only be applied to symbol declarations,
> of which a typedef'd function pointer is not. This would only be useful if a
> function pointer defined in the linked dll is desired t
On Thu, 7 Jul 2022 21:57:42 GMT, Valerie Peng wrote:
> pkcs11.h is a standard header file from OASIS. Best to leave it alone. Just
> my .02.
The only change to pkcs11.h is in a comment though, the other changes are
outside the ANSI C headers from the standard. Should I just revert the comment
On Sat, 2 Jul 2022 02:12:15 GMT, Julian Waters wrote:
> Several instances of function pointers in jdk.crypto.cryptoki are marked with
> the dllimport attribute, which should only be applied to symbol declarations,
> of which a typedef'd function pointer is not. This would only be useful if a
>
Several instances of function pointers in jdk.crypto.cryptoki are marked with
the dllimport attribute, which should only be applied to symbol declarations,
of which a typedef'd function pointer is not. This would only be useful if a
function pointer defined in the linked dll is desired to be imp
Several instances of function pointers in jdk.crypto.cryptoki are marked with
the dllimport attribute, which should only be applied to symbol declarations,
of which a typedef'd function pointer is not. In addition to being incorrect,
at least on the versions of Visual C++ the JDK supports today,
12 matches
Mail list logo
