On Thu Aug 10 15:29:24 2023 +0000, Jacek Caban wrote:
Those patches may be split better. Will ccref ultimately be inside DispatchEx? It probably makes sense to move it before doing traversal conversion. It should be possible to keep using it voluntary. For traversal itself, the describe step should be possible to do based on `dispex_static_data_t`, it already has the name. We could just implement describing on dispex level and not need to worry about it in every object.
If I place ccref in DispatchEx, I'll have to special case it in window (outer windows don't have dispex, so I'll have to conditionally do ccref incr/decr). Is that acceptable?
As for describing the node, the main problem is that the name is in wide chars. I suppose adding an extra name field would be pretty redundant, but I think traversal happens a lot more than toString, not to mention that conversion to ASCII is lossy but not the other way around.
So should I convert the current names to ASCII and then convert them in toString and use them directly in traversal, or convert them in traversal from Wide?