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.6 required=5.0 tests=BAYES_00,TO_NO_BRKTS_FROM_MSSP
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,93ab7fc5388e249
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2001-12-05 07:46:40 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!nntp-relay.ihug.net!ihug.co.nz!out.nntp.be!propagator-SanJose!in.nntp.be!newsranger.com!www.newsranger.com!not-for-mail
Newsgroups: comp.lang.ada
From: Ted Dennison<dennison@telepath.com>
References: <DzdP7.48986$xS6.81471@www.newsranger.com>
 <3C0E1E7E.CA7113F4@brighton.ac.uk>
Subject: Re: List container strawman 1.3
Message-ID: <kjrP7.49771$xS6.82061@www.newsranger.com>
X-Abuse-Info: When contacting newsranger.com regarding abuse please
X-Abuse-Info: forward the entire news article including headers or
X-Abuse-Info: else we will not be able to process your request
X-Complaints-To: abuse@newsranger.com
NNTP-Posting-Date: Wed, 05 Dec 2001 10:46:24 EST
Organization: http://www.newsranger.com
Date: Wed, 05 Dec 2001 15:46:24 GMT
Xref: archiver1.google.com comp.lang.ada:17448
Date: 2001-12-05T15:46:24+00:00
List-Id: <comp.lang.ada>

In article <3C0E1E7E.CA7113F4@brighton.ac.uk>, John English says...
>Ted Dennison wrote:
>> 
>> The latest (1.3) version of the list container strawman is available on my
>> website at
>> http://www.telepath.com/dennison/Ted/Containers-Lists-Unbounded.ads.html .
>
>1) Would it be a good idea to rename the Direction values Front, Back
>   as Forwards, Backwards or To_Front, To_Back to make it clearer
>   what they mean?

I don't think those alternatives would make sense in the case of the list end
insertion routines. However, I'll grant that the terminology makes one of the
other routine parameter names a bit awkward (iterator-based "Remove:). But the
alternatives make it even moreso. I'm also generally not a fan of putting
articles in identifiers. Perhaps that's just an overreaction to seeing people
abuse it by making whole phrases. :-)

There is essentially a choice between biasing the terminology toward ends,
directions, or making two types. I think we should be able to get by without two
types. Biasing it toward directions makes at least two non-defaulted parameters
a bit awkward. Biasing it toward ends makes one defaulted paremeter a little
more awkward (it would still be awkward either way because its a complicated
concept to start with).

What we have right now for usage (assuming instantiation as "Lists") is:
1)
  Lists.Insert
     (Target      => Car_List,
      New_Element => Honda,
      List_End    => Lists.Front);

  Lists.Next
     (Location => Car_Location,
      Toward   => Lists.Front
     );