> So by changing to a simple non-clearing allocator, this is going to force drivers to > be re-written to initialize class member variables in uninitialized memory? (Note: > I'm probably not even close to understanding that correctly).
You're right, you're not even close. Nothing is forcing anything to be "re-written". There are bugs in the drivers that using a non-clearing allocator has exposed. Those bugs are being fixed. Nothing is being "re-written".
Previous 
Index 
Flat 
Re: MAME 0.227 Release Delayed to December 2020
Reply
