From: "Jeffrey R. Carter" <spam.jrcarter.not@spam.not.acm.org>
Subject: Re: Design of cross referring types/classes and proper usage of containers
Date: Tue, 4 Aug 2015 12:20:01 -0700
Date: 2015-08-04T12:20:01-07:00 [thread overview]
Message-ID: <mpr361$b9j$1@dont-email.me> (raw)
In-Reply-To: <3341271b-4926-40cb-a9aa-660522d56f24@googlegroups.com>
On 08/04/2015 12:00 PM, Serge Robyns wrote:
> And I've a final question based on the advise.
>
> Given static (immutable data) one one hand and dynamic data (changed during the execution) on the other hand; stored in various containers. What is actually the best approach? Shall I Storing the full element of objects or references created through new T_xyz?
>
> If I want to use an access variables in the first method, do I need to pass an aliased type?
Your problem does not need access types, and will be clearer and simpler without
them.
You could have maps:
(client ID) -> (client info)
(subscription ID) -> (subscription info)
Client info may contain subscription IDs, and subscription info may contain
client IDs. If you have one and not another, you use the ID to obtain the info.
--
Jeff Carter
"Have you gone berserk? Can't you see that that man is a ni?"
Blazing Saddles
38
next prev parent reply other threads:[~2015-08-04 19:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 16:08 Design of cross referring types/classes and proper usage of containers Serge Robyns
2015-08-03 16:14 ` Serge Robyns
2015-08-03 20:17 ` Georg Bauhaus
2015-08-03 16:22 ` Dmitry A. Kazakov
2015-08-04 11:43 ` Serge Robyns
2015-08-04 12:13 ` Dmitry A. Kazakov
2015-08-04 19:00 ` Serge Robyns
2015-08-04 19:20 ` Jeffrey R. Carter [this message]
2015-08-04 20:27 ` Randy Brukardt
2015-08-04 21:21 ` Simon Wright
2015-08-08 11:25 ` Serge Robyns
2015-08-09 3:11 ` Randy Brukardt
2015-08-09 13:33 ` Serge Robyns
2015-08-05 7:37 ` Dmitry A. Kazakov
2015-08-05 17:51 ` Serge Robyns
2015-08-05 19:21 ` Dmitry A. Kazakov
2015-08-06 7:00 ` Georg Bauhaus
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox