Mixing
Type definitions and the size of various types on multi-platform distributions
I'm slightly confused by the PKCS11Interop library's use of types across different OS platforms. My understanding is that the size of a long on Windows x64 is 4 bytes but on Linux/iOS 64bit the length is 8 bytes. This is indeed reflected in the Platform.cs implementation of the public static NativeULongSize. However looking at the LowLevelAPIXX source, where for example LowLevelAPI80 corresponds to Linux (x64), and LowLevelAPI81 corresponds to Windows (x64), the defintion of NativeULong used in the structure defintions is UInt64 - and so will be 8 bytes. Is this a mistake - at the very least it seems to be inconsistent?
pkcs11interop
asked Jan 2 at 8:56
Robert JackRobert Jack
61
add a comment |
I'm slightly confused by the PKCS11Interop library's use of types across different OS platforms. My understanding is that the size of a long on Windows x64 is 4 bytes but on Linux/iOS 64bit the length is 8 bytes. This is indeed reflected in the Platform.cs implementation of the public static NativeULongSize. However looking at the LowLevelAPIXX source, where for example LowLevelAPI80 corresponds to Linux (x64), and LowLevelAPI81 corresponds to Windows (x64), the defintion of NativeULong used in the structure defintions is UInt64 - and so will be 8 bytes. Is this a mistake - at the very least it seems to be inconsistent?
pkcs11interop
asked Jan 2 at 8:56
Robert JackRobert Jack
61
Looking again at the source, it is my mistake. I had (incorrectly) assumed that the LowLevelAPI81 corresponded to Windows x64 which actually doesn't seem to be the case. The selection of OS is the platform module for windows is based on the existence of the environment variable "windir". The IntPtr size is handled by the .NET runtime. Apologies for the rather stupid suggestion that it might be a mistake - this is an incredible library.
– Robert Jack
Jan 2 at 9:27
add a comment |
I'm slightly confused by the PKCS11Interop library's use of types across different OS platforms. My understanding is that the size of a long on Windows x64 is 4 bytes but on Linux/iOS 64bit the length is 8 bytes. This is indeed reflected in the Platform.cs implementation of the public static NativeULongSize. However looking at the LowLevelAPIXX source, where for example LowLevelAPI80 corresponds to Linux (x64), and LowLevelAPI81 corresponds to Windows (x64), the defintion of NativeULong used in the structure defintions is UInt64 - and so will be 8 bytes. Is this a mistake - at the very least it seems to be inconsistent?
pkcs11interop
asked Jan 2 at 8:56
Robert JackRobert Jack
61
I'm slightly confused by the PKCS11Interop library's use of types across different OS platforms. My understanding is that the size of a long on Windows x64 is 4 bytes but on Linux/iOS 64bit the length is 8 bytes. This is indeed reflected in the Platform.cs implementation of the public static NativeULongSize. However looking at the LowLevelAPIXX source, where for example LowLevelAPI80 corresponds to Linux (x64), and LowLevelAPI81 corresponds to Windows (x64), the defintion of NativeULong used in the structure defintions is UInt64 - and so will be 8 bytes. Is this a mistake - at the very least it seems to be inconsistent?
pkcs11interop
pkcs11interop
asked Jan 2 at 8:56
Robert JackRobert Jack
61
asked Jan 2 at 8:56
Robert JackRobert Jack
61
asked Jan 2 at 8:56
Robert JackRobert Jack
61
asked Jan 2 at 8:56
Robert JackRobert Jack
61
asked Jan 2 at 8:56
Robert JackRobert Jack
61
61
Looking again at the source, it is my mistake. I had (incorrectly) assumed that the LowLevelAPI81 corresponded to Windows x64 which actually doesn't seem to be the case. The selection of OS is the platform module for windows is based on the existence of the environment variable "windir". The IntPtr size is handled by the .NET runtime. Apologies for the rather stupid suggestion that it might be a mistake - this is an incredible library.
– Robert Jack
Jan 2 at 9:27
add a comment |
Looking again at the source, it is my mistake. I had (incorrectly) assumed that the LowLevelAPI81 corresponded to Windows x64 which actually doesn't seem to be the case. The selection of OS is the platform module for windows is based on the existence of the environment variable "windir". The IntPtr size is handled by the .NET runtime. Apologies for the rather stupid suggestion that it might be a mistake - this is an incredible library.
– Robert Jack
Jan 2 at 9:27
Looking again at the source, it is my mistake. I had (incorrectly) assumed that the LowLevelAPI81 corresponded to Windows x64 which actually doesn't seem to be the case. The selection of OS is the platform module for windows is based on the existence of the environment variable "windir". The IntPtr size is handled by the .NET runtime. Apologies for the rather stupid suggestion that it might be a mistake - this is an incredible library.
– Robert Jack
Jan 2 at 9:27
Looking again at the source, it is my mistake. I had (incorrectly) assumed that the LowLevelAPI81 corresponded to Windows x64 which actually doesn't seem to be the case. The selection of OS is the platform module for windows is based on the existence of the environment variable "windir". The IntPtr size is handled by the .NET runtime. Apologies for the rather stupid suggestion that it might be a mistake - this is an incredible library.
– Robert Jack
Jan 2 at 9:27
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54003528%2ftype-definitions-and-the-size-of-various-types-on-multi-platform-distributions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54003528%2ftype-definitions-and-the-size-of-various-types-on-multi-platform-distributions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Looking again at the source, it is my mistake. I had (incorrectly) assumed that the LowLevelAPI81 corresponded to Windows x64 which actually doesn't seem to be the case. The selection of OS is the platform module for windows is based on the existence of the environment variable "windir". The IntPtr size is handled by the .NET runtime. Apologies for the rather stupid suggestion that it might be a mistake - this is an incredible library.
– Robert Jack
Jan 2 at 9:27