You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. python-3.x), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
default
std::wstringis not valid in C-linkage functions. Now, warnings aren't errors. But when I run it, calling that function results in a crash. It's the same place Python crashes viactypes, so at least I reached parity. Now I'm left wondering whether the issue is related to the wstring and C linkage; or the other possibility is that some internal state of the library is wrong, and I'd have to figure that out first.extern "C"? If so, stop doing that. I can confirm that markingfasextern "C"here seems to make it give wrong codegen. So the fix is don't do that, then.wstring. What does that bunch of bytes look like in hex? (Define your ownstruct WString { alignas(8) char bytes_[sizeof(std::wstring)]; ~WString() {} };and print out the bytes. This could show that (contrary to my expectation) the DLL was built with a different idea of whatwstringis than what's in your current platform's Microsoft STL.