From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,2fa4069595cb9ef7
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!postnews.google.com!l11g2000yqb.googlegroups.com!not-for-mail
From: Gene <gene.ressler@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Breaking a circularity
Date: Mon, 28 Mar 2011 15:26:29 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: 
 <bba26338-e630-4e14-9f2a-562af36e3d9e@l11g2000yqb.googlegroups.com>
References: 
 <dd0c7179-9e48-4366-9b1f-c5586b2c6e3c@e21g2000yqe.googlegroups.com>
 <0477ecf8-3ff0-4511-82af-f38587704ca3@l11g2000yqb.googlegroups.com>
NNTP-Posting-Host: 134.240.241.2
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: posting.google.com 1301351189 27062 127.0.0.1 (28 Mar 2011 22:26:29
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 28 Mar 2011 22:26:29 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: l11g2000yqb.googlegroups.com; posting-host=134.240.241.2;
 posting-account=-BkjswoAAACC3NU8b6V8c50JQ2JBOs04
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64;
 Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.30729; InfoPath.2; .NET
 CLR 3.5.30729; .NET4.0C; .NET4.0E),gzip(gfe)
Xref: g2news2.google.com comp.lang.ada:19529
Date: 2011-03-28T15:26:29-07:00
List-Id: <comp.lang.ada>

> 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.