Content deleted Content added
→Which device classes?: new section |
→Interfaces vs. Implementations: new section |
||
Line 12:
"UMDF facilitates the creation of drivers for certain classes of devices." Which device classes should be mentioned. - [[User:xpclient|<small>xpclient</small>]] <sup>[[User talk:xpclient|<small>Talk</small>]]</sup> 08:14, 6 October 2008 (UTC)
== Interfaces vs. Implementations ==
IDriverEntry and IDevicePnpHardware are shown as stub implementations. I'd think it would make more sense to only show the class interface, and no (useless and empty) implementations. It might also make sense to enumerate all interface methods, and give a brief summary on what the two interfaces do, and which methods get called in which order by UMDF, to give an overview how those drivers are loaded and operate. However, I do not possess the inside knowledge to write this.
Also, classes do not need to derive from CUnknown, it is only one of many possibilities to write COM-components. I would also give information about the purpose of IUnknown (... "reference counting and querying for other interfaces" ...). [[Special:Contributions/88.215.67.7|88.215.67.7]] ([[User talk:88.215.67.7|talk]]) 03:38, 14 January 2009 (UTC)
| |||