> Right. My point was that assembler would hurt simply because it's an order of > magnitude more time-intensive to write and debug.
It will certainly make it harder to write, but it would be wrong to suggest that language choice has some magic ability to make an emulator more accurate.
> That's less likely now than it was when we started MAME (only nutters like myself > commonly run machines over 4 GHz) but we're slowly learning to take advantage of > multicore.
It will be interesting to see what comes in another ten years, but currently there doesn't look like they'll be the same jump in performance that we have had since the 486 days.
> The real issue is these modern CPUs are so smart about reworking your code > "live" for optimization that hand-tuning is mostly irrelevant.
They've hit the same problem, it's now hard to just ramp the clock speed so they are having to find better algorithms to make code run faster. As there is a lot of C++ code out there then I'd expect to see improvements in compilers and the processors ability to run the generated code faster. Which of course you also don't get the benefit if you write in assembler.
Previous 
Index 
Next 
Flat 
Re: Should I learn C or C++?
Reply
