MAMEWorld Forums - EmuChat - Re: The explanation is new...

> isn't it? I don't recall/didn't see anyone providing that in the 'MAME in your
> browser' thread, here.

I linked it when it was announced.

> Quite interesting, even for me who does no coding. Intriguing was (seemingly to me)
> how little code resulted and how little time it took them.

As the portability guy, I'm vaguely insulted that you'd find that remarkable. MAME compiles out of the box on every major OS/environment shipping today and a few that aren't. If you have GCC and SDL available, the rest is negotiable.

> - how does the lack of CPU emulation based on the UDR affect emulation accuracy?

They removed all of the drivers that relied on the UML subsystem. That wasn't actually necessary since there is a pure C backend which does conventional interpretive emulation on the intermediate UML bytecode. You lose all the speed of the recompiler plus some doing that of course, but the accuracy is just as good as in the conventional case.

> - how does their enabling of SDL (or does it?) parallel SDLMAME?

They used the existing SDL backend largely unmodified (but with OpenGL disabled). The SDL backend is intended to work on pretty much anything SDL can be ported to.