From: Gene <gene.ressler@gmail.com>
Subject: Re: Breaking a circularity
Date: Mon, 28 Mar 2011 15:26:29 -0700 (PDT)
Date: 2011-03-28T15:26:29-07:00 [thread overview]
Message-ID: <bba26338-e630-4e14-9f2a-562af36e3d9e@l11g2000yqb.googlegroups.com> (raw)
In-Reply-To: 0477ecf8-3ff0-4511-82af-f38587704ca3@l11g2000yqb.googlegroups.com
> Better names might help too, why expose that it is a 'wrapper' to the
> user? I'd probably call what I have a '_Wrapper' as 'Event_Queue' and
> then find a better name for the Event_Queues - Event_Queues_With_State
> perhaps.
>
> -- Martin-
Thanks. But the only routine that needs to mention "Wrapper" is the
initializer
for the State. In this case, Wrapper says pretty clearly what's going
on.
Throughout all other code, it's
State.Future_Events.Queue
which is pretty clear as well.
next prev parent reply other threads:[~2011-03-28 22:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 4:11 Breaking a circularity Gene
2011-03-28 9:59 ` Ludovic Brenta
2011-03-28 11:37 ` Simon Wright
2011-03-28 22:38 ` Gene
2011-03-29 3:01 ` Randy Brukardt
2011-03-28 19:47 ` Gene
2011-03-28 10:15 ` Simon Wright
2011-03-28 21:31 ` Gene
2011-03-28 11:06 ` Martin
2011-03-28 22:26 ` Gene [this message]
2011-03-29 16:28 ` Martin
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox