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

Register component as interface or specific base class identifier? #28

Open
Glidias opened this issue Apr 10, 2017 · 0 comments
Open

Register component as interface or specific base class identifier? #28

Glidias opened this issue Apr 10, 2017 · 0 comments

Comments

@Glidias
Copy link

Glidias commented Apr 10, 2017

From the API, doesn't seem to support it. From the code, it appears as if it's always meant to using base class implementation as identifier for given component type?

Why does the macro consider s=superClass to have a possibility of being IComponent? This will never happen because IComponent is an interface, not a class, anyway (I think, from what i remembered with superClass).

Also, when I use reference-based typedef instead for View<T> (eg. typedef SomethingReusable = { } ) , it doesn't work properly when I wish the macro was also capable of determining the component fields from typedefs, class fields, etc. besides anonymous structure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant