> In a project like MAME any documentation never keeps up with the changes to the code. And what is even worse than no documentation is misleading documentation. I know that's a lame excuse. But this is a non-commercial project. Resources are scarce and devs prefer to focus on inventing new things instead of writing documentation in their spare time.
I remember drivers in the old days being written according to fairly different approaches. What standards, if any, have Aaron's, etc, contributions since .107 made/required in writing drivers?
Scifi frauds. SF illuminates.
_________________
Culture General Contact Unit (Eccentric)
|
Index 
Flat 
Re: MAME theory of operation
Reply
