-
Notifications
You must be signed in to change notification settings - Fork 511
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix bug in COM interface chain support #3060
Merged
sivadeilra
merged 1 commit into
microsoft:master
from
sivadeilra:user/ardavis/fix-interface-chains
May 29, 2024
Merged
Fix bug in COM interface chain support #3060
sivadeilra
merged 1 commit into
microsoft:master
from
sivadeilra:user/ardavis/fix-interface-chains
May 29, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The definition of a COM interface may inherit from another interface. These are known as "interface chains". The `#[implement]` macro allows designers to specify only the minimal set of interface chains that are needed for a given COM object implementation. The `#[implement]` macro (and the `#[interface]` macro) work together to pull in the implementations of all interfaces along the chain. Unfortunately there is a bug in the implementation of `QueryInterface` for interface chains. The current `QueryInterface` implementation will only check the IIDs of the interfaces at the root of the chian, i.e. the "most-derived" interface. `QueryInterface` will not search the IIDs of interfaces that are in the inheritance chain. This bug is demonstrated (detected) by the new unit tests in `crates/tests/implement_core/src/com_chain.rs`. This PR fixes the bug by generating an `fn matches()` method that checks the current IID and then checks the parent interface (if any) by calling its `match()` method. This fixes the unit test.
'matches' definitely needs to check parent IIDs. |
dpaoliello
approved these changes
May 29, 2024
arlosi
approved these changes
May 29, 2024
wravery
approved these changes
May 29, 2024
kennykerr
reviewed
Jun 4, 2024
// QueryInterface to work correctly for all interfaces in an inheritance chain, e.g. | ||
// IFoo3 derives from IFoo2 derives from IFoo. | ||
// | ||
// We avoid matching IUnknown because object identity depends on the uniqueness of the IUnknown pointer. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May be worth adding a test for this. #3069
mati865
pushed a commit
to mati865/windows-rs
that referenced
this pull request
Jun 15, 2024
The definition of a COM interface may inherit from another interface. These are known as "interface chains". The `#[implement]` macro allows designers to specify only the minimal set of interface chains that are needed for a given COM object implementation. The `#[implement]` macro (and the `#[interface]` macro) work together to pull in the implementations of all interfaces along the chain. Unfortunately there is a bug in the implementation of `QueryInterface` for interface chains. The current `QueryInterface` implementation will only check the IIDs of the interfaces at the root of the chian, i.e. the "most-derived" interface. `QueryInterface` will not search the IIDs of interfaces that are in the inheritance chain. This bug is demonstrated (detected) by the new unit tests in `crates/tests/implement_core/src/com_chain.rs`. This PR fixes the bug by generating an `fn matches()` method that checks the current IID and then checks the parent interface (if any) by calling its `match()` method. This fixes the unit test. Co-authored-by: Arlie Davis <ardavis@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The definition of a COM interface may inherit from another interface. These are known as "interface chains". The
#[implement]
macro allows designers to specify only the minimal set of interface chains that are needed for a given COM object implementation. The#[implement]
macro (and the#[interface]
macro) work together to pull in the implementations of all interfaces along the chain.Unfortunately there is a bug in the implementation of
QueryInterface
for interface chains. The currentQueryInterface
implementation will only check the IIDs of the interfaces at the root of the chian, i.e. the "most-derived" interface.QueryInterface
will not search the IIDs of interfaces that are in the inheritance chain.This bug is demonstrated (detected) by the new unit tests in
crates/tests/implement_core/src/com_chain.rs
. This PR fixes the bug by generating anfn matches()
method that checks the current IID and then checks the parent interface (if any) by calling itsmatch()
method. This fixes the unit test.