From: Roy S. <roy...@ic...> - 2018-07-05 14:11:20
|
On Thu, 5 Jul 2018, Renato Poli wrote: > >> It sounds like you'd rather be doing a tuple<int, int, int, int>? > Well, that would be my second shot, which I consider dusty but healthy. > *Ideally* I would do a MyClass { int p1; int p2; int p3; int p4; }. I'm afraid handling *that* automatically is not going to be possible until C++ adds reflection support. In C++20, fingers crossed... > >> I'll try setting up a unit test with that and see if I can fix ... > There's no need to hurry. I moved forward with the nested pairs. > I wrapped it with access functions (p.second.second.second is the deepest raw int). Thanks for the update! --- Roy |