FFI / MemoryPointer Memory Allocation?

Ruby FFI tries to be symmetric about who owns memory - if you allocate it (i.e. The C code), you have to free it. Conversely, if FFI allocates it, it alone can free it.

I think that in many ffi, whichever language you use, values of builtin types (like strings) must be constructed using specially provided runtime functions. Ruby abides to this rule.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.