I expect to have a deliberately placed chunk of code added now to break my build, again.
See, I can’t win. On one side I’ve got Olivier telling me I’m not migrating MAME to pre-standard C++20 fast enough, and on the other hand I’ve got you complaining that you can’t build MAME if you refuse to update to a toolchain that isn’t over three years old. I try to strike the middle ground, and everyone’s angry at me. I’m not intentionally breaking your build, I’m making the most of more expressive language features to make life easier for contributors. It shows in the increased number of contributors, increased quality of submissions, and the almost complete absence of whole classes of issues that used to plague MAME development. Remember the dreaded late bind errors, and devices not being found? They were a huge waste of contributors’ time before C++ machine configuration, but they’ve all but disappeared now. Do you remember the pages of MCFG_ macros that you needed to write along with a device class? They’ve been completely eliminated – stuff just works without a pile of unnecessary work.
What do you have to contribute here besides a wishlist? Anyone can wish, anyone can say a feature would be nice to have, anyone say things need to be better. You haven’t said anything in this thread that we don’t already know. What are you actually going to do to move things forward?