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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.107.4.10 with SMTP id 10mr2954761ioe.35.1511993938946; Wed, 29 Nov 2017 14:18:58 -0800 (PST) X-Received: by 10.157.1.175 with SMTP id e44mr99348ote.1.1511993938872; Wed, 29 Nov 2017 14:18:58 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!border1.nntp.ams1.giganews.com!nntp.giganews.com!peer02.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.am4!peer.am4.highwinds-media.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!i6no23368itb.0!news-out.google.com!193ni3iti.0!nntp.google.com!193no20582itr.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 29 Nov 2017 14:18:58 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=155.148.6.150; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC NNTP-Posting-Host: 155.148.6.150 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Encaspulation: What to export From: Shark8 Injection-Date: Wed, 29 Nov 2017 22:18:58 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Received-Body-CRC: 1821854723 X-Received-Bytes: 2323 Xref: reader02.eternal-september.org comp.lang.ada:49268 Date: 2017-11-29T14:18:58-08:00 List-Id: On Wednesday, November 29, 2017 at 1:42:07 PM UTC-7, Randy Brukardt wrote: >=20 > >... For example recursive descent may analyze the same fragment of a tr= ee > > more than once or it may skip some parts of the tree entirely. >=20 > That's not "recursive descent", that's just some code doing whatever it i= s=20 > that you need to do. Nothing wrong with that, but calling that "parsing" = or=20 > "recursive descent" or anything other well-known term is just abusing tho= se=20 > terms. I'd suggest "tree transformation"... except that somewhat implies that the = result is the same type of tree [like a Procedure Transform( Item : in out = Tree )] when it sounds like he's converting some other sort of tree into th= e sort he wants [like a Function Convert( Input : RDF_Tree ) return Whateve= r_Tree]. Perhaps "Tree Conversion" then?