Great news for windows users , CPP is ported to Windows. Again like linux and macos it has its own class called "CPPBridgeWin" where all Windows methods are located and comes with two examples with reading and writing to the shared memory.
In your github-cache of your pharo folder inside the CPP subfolder you will find two subfolders one called simply CPP which shows the Windows Visual C++ version of writing and create the shared memory and a CPPReceive subfolder that contains the Windows Visual C++ version for reading from the shared memory . Both come with their own project files so they can be opened easily inside Visual Studio Community edition which is free to download and use. Both are tested on latest 64 bit Windows 10. One thing I forgot to mention and this applies to the whole CPP project is that C++ is completely optional. That means that shared memory could be shared instead of between a C++ application and Pharo application , instead we can have multiple pharo images executing at the same time sharing the same exact memory. This is useful for those of you who work with very big data and you dont like the idea of it being garbage collected or copied in all your images running at the same time. This way you save memory , you have access to manual memory management with all its pitfalls (yes a wrong pointer will crash your pharo application in an instant) and advantages (it does not get any faster than shared memory with manual memory management, this is the method your OS uses to do pretty much everything data orientated and for loading DLLs). Because CPP supports file mapping that means the data is auto saved into the file , one file for all pharo images running at the same time , this way you can store the live state like you do with a regular pharo image and feel safe that you will never need to worry about forgeting to save the file like you do with pharo images. Essentially that means you can completely bypass C++ and do it all in just pharo code. As always everything is commented and documented . --- Αυτό το e-mail ελέγχθηκε για ιούς από το πρόγραμμα Avast antivirus. https://www.avast.com/antivirus
