Ariel Vina-Rodriguez
Ariel Vina-Rodriguez
> the dereference of pointers coming from casts between detail::window_handle_impl* Did you found any dereference of those pointers? I thought it is a "handler", which is something with the only...
The win32 API is an old c API which (ab)use extensively conversion of pointers to void*. Do you know how to deal with that?
Could you show how exactly are you building and linking nana and the executables?
Surely there are errors in nana, but in relation to reinterpret_cast: it was invented to deal with the low level code, the type of code used in the implementation of...
>owner and parent arguments are of type window: but they are pointers obtained from a basic_window reinterpreted as window. No aliases problem here.
>Not all pointers are unique. Certain types (for example, any cv-qualification variations of char and unsigned char) are excluded from aliasing requirements. Note that the sole fact that the type...
The original VALUE of the pointer, the only object created is a `basic_window `. The pointer to this object is reinterpreted to `window ` and then back to `basic_window `...
I dont see why you assume this is an intention to do tag dispatching
What I see is an API hiding a type that is an implementation detail it dont want to leake. An uses the value of a pointer as a "handler" or...
Are you compiling nana with your project or are you using a precompiled nana?