Ah. I see.
This seems like one of those object oriented design issues... inheritance vs composition.
They shouldn't extend from a BIOS, they should contain (or use) a BIOS.
Instead of:
BIOS --> parent game --> clone game
It should be something like:
parent game (uses BIOS) --> clone game (uses BIOS)
The problem is that a BIOS is not a game, but it's treated as one in MAME so that sets can "inherit" from them as they would a parent set.
From a software design standpoint, I think that the GAME macro should have a separate parameter for a BIOS for games that require one.
The other option is to make every parent set include the BIOS ROMs, but I assume avoiding that was exactly why we ended up with the design that we currently have in MAME.
GroovyMAME support forum on BYOAC
|
Index 
Flat 
Re: Question about DECO cassette artwork...
Reply
.lay files for the missing DECO cassette artwork...
