Date: Fri, 25 Nov 2022 15:29:00 +0000
On Friday, November 25, 2022, Jason McKesson via Std-Proposals <
std-proposals_at_[hidden]> wrote:
> There seems to be a broad lack of understanding of what this feature
> is doing, probably due to unfamiliarity with the way the wxWidgets
> library uses base classes.
>
> wxWidgets uses multiple inheritance in a lot of cases. The two classes
> in question, `wxControl` and `wxTextEntry` are both base classes. A
> control that wants to have text entry functionality would inherit from
> both, but it is also possible to have text entry objects that are not
> controls and controls that don't have text entry functionality.
>
> The goal of the proposal is to be able to write a function that takes
> a single pointer to any type which inherits from *two or more* base
> classes. And then use that pointer to access any function which is
> available from any of these base classes.
<snip>
Thanks James, you hit the nail on the head here. What you wrote is
_exactly_ what I'm thinking.
std-proposals_at_[hidden]> wrote:
> There seems to be a broad lack of understanding of what this feature
> is doing, probably due to unfamiliarity with the way the wxWidgets
> library uses base classes.
>
> wxWidgets uses multiple inheritance in a lot of cases. The two classes
> in question, `wxControl` and `wxTextEntry` are both base classes. A
> control that wants to have text entry functionality would inherit from
> both, but it is also possible to have text entry objects that are not
> controls and controls that don't have text entry functionality.
>
> The goal of the proposal is to be able to write a function that takes
> a single pointer to any type which inherits from *two or more* base
> classes. And then use that pointer to access any function which is
> available from any of these base classes.
<snip>
Thanks James, you hit the nail on the head here. What you wrote is
_exactly_ what I'm thinking.
Received on 2022-11-25 15:29:02