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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,a644fa9cd1a3869a X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-11-12 14:52:59 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!jfk3-feed1.news.digex.net!dca6-feed2.news.digex.net!intermedia!newsfeed1.cidera.com!Cidera!cyclone1.gnilink.net!news-east.rr.com!cyclone.kc.rr.com!news.kc.rr.com!news-west.rr.com!lsnws01.we.mediaone.net!typhoon.san.rr.com!not-for-mail Message-ID: <3BF052D3.ECEF3FF2@san.rr.com> From: Darren New Organization: Boxes! X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: List container strawman 1.2 References: <3BECA3B7.5020702@telepath.com> <3BF0247D.4500975E@san.rr.com> <5BXH7.22252$xS6.34813@www.newsranger.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 12 Nov 2001 22:53:25 GMT NNTP-Posting-Host: 66.75.151.160 X-Complaints-To: abuse@rr.com X-Trace: typhoon.san.rr.com 1005605605 66.75.151.160 (Mon, 12 Nov 2001 14:53:25 PST) NNTP-Posting-Date: Mon, 12 Nov 2001 14:53:25 PST Xref: archiver1.google.com comp.lang.ada:16378 Date: 2001-11-12T22:53:25+00:00 List-Id: Ted Dennison wrote: > I can't always read all parts of a MIME message w/ my regular newsreader. In > this case, your spec came through as garbage. Sorry. MIME's been around for longer than Ada95, so I figured everyone could handle it. The plaintext version is pasted at the bottom, then. > Perhaps. But then First and Last make perfect sense in terms of iterating, and > make it clearer which way "Next" and "Previous" go, so I think the terminology > there is better. "Font" and "Back" are pretty standard terminology for list > ends, so from that standpoint they should stay too. What would you prefer to see > here? OK, well, is the front of the list the first element? If so, why do they need different names? Just because there's two common terminologies, that doesn't mean both should be used in the same library. :-) Pick either "first" for the start of the list or "front" for the start of the list, but not both. Especially not both with different signatures. > >I do it all the time in list-oriented languages. When you have a bunch > >of lists you want to merge into one, it's very handy. It makes no sense > >to leave it out, really, since it's not something you can easily code up > >yourself. > > If all you want is to tack them together, the "&" functions do that just fine. > Do you actually need to merge lists by sticking one into a specific place in the > middle of the other all the time? It's not uncommon, usually when the sub-lists being inserted "mean" different things, like you're inserting the children of the directory after the directory entry during a breadth-first walk, say. And "&" has the overhead of copying both lists, as well. > Making them procedures and/or limited > really buys you nothing, and prevents some very useful constructions for those > of us who like to do all the work we can in our declaration sections. OK, that makes sense. I'll grant that I'm not familiar enough with Ada programming to call that one. :-) -- Darren New San Diego, CA, USA (PST). Cryptokeys on demand. You will soon read a generic fortune cookie.