Re: [pkcs11] CK_ULONG considered harmful?

[Tim Hudson <tjh@cryptsoft.com>]

Suggesting changing a variably defined type (CK_ULONG as a long) to
another variably defined type (size_t) is a pretty pointless exercise
IMHO that solves nothing in terms of portability of the interface
between 32-bit and 64-bit platforms or for a simple network protocol
encoding.

However as this isn't a v2.40 topic I suggest we save the real debate
(and associated polls) for after we lock down the v2.40 work.
Changing CK_ULONG isn't within the scope of v2.40 as I understand the
consensus from the face to face discussions.
If there are disagreements on what should or should not be in scope for
v2.40 then we should have a straw poll to settle that issue.

Thanks,
Tim.