Timeline for Using vectors of shared pointers to objects in my C++ code to prevent object duplication
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 11, 2017 at 8:51 | comment | added | Doc Brown |
We already discussed this in the OPs former question - no single Particle is owner of one Contact object, since a contact is associated to two different particles. So when requesting the set of contacts of those two particles, the intersection of those sets should contain the common Contact object.
|
|
| Nov 11, 2017 at 5:31 | comment | added | AnInquiringMind |
That's an interesting suggestion. I wonder if there is any performance concerns with doing such a successive "encapsulation". As for Particle objects containing a list of its contacts, the point is that the Network object entirely decides the relationship between particles and contacts, so all the related data should be accessible solely through the Network object.
|
|
| Nov 11, 2017 at 4:23 | history | answered | user1118321 | CC BY-SA 3.0 |