Some aid comes from making the list of lists be just a simple
std::set<std::string> where the contained string is a sorted list of space separated pins. This gets pretty easy then. Can you then support: base class: (pin_merge A B) derived class: (pin_merge B A C D) The remaining problem is that you do not know what to look up, there is no separator between AB (old) & CD (new) The list of lists may not be the only path to persue. Another idea might be to put an integer "merge_code" in each pin, and tie the pins together that way. The merge_code is simply a number that increments uniquely within each PART for each *unique*, not additive merge list. The merge_code for pins not merged could be zero. Probably still missing something, but again, coder decides. _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
