On Fri Feb 17 10:27:31 2023 +0000, Huw Davies wrote:
I think I'd like to wait for @piotr to finish his work on wineps.drv otherwise this is going to cause conflicts. One related issue is that of `PSDRV_Heap`. This was introduced to provide an easy (and quick) way to free the global data as wineps.drv could in principle be loaded / unloaded many times. With the config_module changes in winspool, which essentially pin wineps.drv in place, this has become less of an issue, so we should likely review this.
FWIW I don't might if it goes into wine before my changes.
Please note that I'm currently using wineps.drv on Windows for testing (only as print processor). I guess that since this is a user-mode driver it will work with malloc. At some point, when we have correct architecture for graphics driver, we will need to migrate it to EngAllocMem/EngFreeMem. That's why I'm not sure if it makes sense to migrate it to CRT memory functions.