>>> If you avoided the static CRT, and only used Windows APIs, that would >>> avoid this issue, but that means reimplementing everything - >>> malloc/free, FILE*, stdin/stdout/stderr, etc etc. I don't think anyone >>> is contemplating that. >> Actually, I am. > > I stand corrected :-) If you need any help, I'd be willing to assist.
It's a long-term project. If you are curious, I would recommend you look into memory management. At a minimum, pymalloc should use VirtualAlloc instead of malloc - as that can guarantee page alignment out of the box (at the same time, mmap should be used on Unix). For variable-sized blocks, you could try HeapAlloc, probably on the process heap. My only concern would be whether HeapAlloc can compete with the CRT's malloc performance-wise. However, during the implementation, additional issues might come up. Regards, Martin _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
