On Thu Oct 9 16:57:58 2025 +0000, Jacek Caban wrote:
This doesn't fix mentioned cycle on its own. We don't have JS/CC integration yet, so JS is not part of the CC graph anyway. Let's wait with the CC change until it makes sense. As for sharing, it would perhaps be more interesting to have entire `IEnumVARIANT` interface shared instead of splitting it halfway. The caller could just pass a vtbl with `get_length(disp)` and `get_item(disp,index)` and remaining functions could be shared on top of that.
Ah right. I had some problems with the attribute collection though, since it uses relative next/skip. I added optional next/skip methods in the vtbl for that but I'm not sure if it's the best way, I can use them for all the others too if you prefer.