> Specifically the "driver_device" "pacman_state" field use.
as you might notice, most variables/handlers used in drivers are now part of a C++ class, specific of the driver. among other things, we are migrating to the driver classes also some initialization code, including the functions usually hidden behind MACHINE_START/MACHINE_RESET/DRIVER_INIT macros
However, in order to move the DRIVER_INIT ones into the class, we needed the GAME macro to be aware of a 'reference' class where to find the DRIVER_INIT function. As such, if a driver had no DRIVER_INIT function in the old code, it just references the generic "driver_device" class...
> There is in somewhere an updated version of the guide for developers in mamedev?
no there is not
|
Index 
Flat 
Re: A silly question about Mame drivers structure.
Reply
