-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question About Usage #57
Comments
Hello @unclepaul84, I'm thrilled that you're giving mio a go! Unfortunately serialization is not supported, mio serves as a thin wrapper around the platform memory mapping facilities, which also don't provide this feature, afaik. This could be a feature on top of mio, a serialization framework, but I think it may be better suited as a separate library to keep separation of concerns clearer. Happy to accept feedback, of course. |
I would need this too (reading only). |
What I have currently:
|
I'm doing exactly what @privefl suggested and it works. When the original file is created sizeof(indval) bytes is written to disk. This will include any padding bytes added by the compiler. It's just a binary blob of bytes. As long as you use the same padding the bytes on disk and in memory are the same. This is highly non portable of course |
I've finally used two doubles, for safety. |
Hello,
Let me apologize in advance for dumb question.
I am trying to figure out a cross-platform way to store and access structs via memory mapped files.
I guess the question is how do I perform operations with mio on types wider than byte or char?
Thanks in Advance
The text was updated successfully, but these errors were encountered: