Skip to content
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

ComInterface ignores property-list of dispinterfaces. #3353

Closed
robodude666 opened this issue Sep 4, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@robodude666
Copy link

commented Sep 4, 2017

It appears that ComInterface does not look at "properties" defined by a dispinterface:

[
    [attributes]
]
dispinterface dispinterface-name
{
    properties:
        property-list
    methods:
        method-list
};

This seems due to the fact it only looks at FUNCDESC records. The "properties" section is what ComModule considers as "Fields" (and are stored as VARDESC records).

While it is certainly confusing being able to define properties in two places, Microsoft does claim it is legal:

You can declare properties in either the properties or methods lists.

By not importing both "Fields" and "Members" we're potentially missing a lot of an interface's capabilities.

@robodude666

This comment has been minimized.

Copy link
Author

commented Sep 4, 2017

Would there be any better solution besides adding a Fields member to ComInterface/ComMember ? Looking through the docs of VARDESC and FUNCDESC they seem different enough that it may be challenging (i.e. messy) maintaining only a single class that's capable of importing from both structures.

@ThunderFrame

This comment has been minimized.

Copy link
Member

commented Sep 4, 2017

Duplicate of #3326

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.