DEVBLK cleanup #288
Labels
Discussion
Developers are invited to discuss a design change or solution to a coding problem.
Enhancement
This issue does not describe a problem but rather describes a suggested change or improvement.
The DEVBLK structure is completely cluttered with device dependent artifacts which are only actually of use for the device handler in charge of the emulation of the device.
This means that every time a device is created it carries around the entire package of ALL the devices known and supported.
My proposal is the DEVBLK should have a single pointer field to an opaque structure that is only relevant to the device handler using it.
This can be achieved incrementally, handler by handler, tested.
Another advantage is that creating a new device handler/emulator would no longer require making any changes to DEVBLK.
Thoughts?
The text was updated successfully, but these errors were encountered: