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.224.86.200 with SMTP id t8mr64240513qal.0.1374892379899; Fri, 26 Jul 2013 19:32:59 -0700 (PDT) X-Received: by 10.50.13.105 with SMTP id g9mr76873igc.9.1374892379754; Fri, 26 Jul 2013 19:32:59 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.bbs-scene.org!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!gh1no14744qab.0!news-out.google.com!dk8ni3qab.0!nntp.google.com!cb17no15556qab.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 26 Jul 2013 19:32:59 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=69.20.190.126; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC NNTP-Posting-Host: 69.20.190.126 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <42dc042d-e458-42a4-abb7-23907982b88f@googlegroups.com> Subject: Re: Problem with limited with From: Shark8 Injection-Date: Sat, 27 Jul 2013 02:32:59 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:16541 Date: 2013-07-26T19:32:59-07:00 List-Id: On Friday, July 26, 2013 6:17:21 PM UTC-6, Jeffrey Carter wrote: >=20 > But even in that case, I'd still say the best solution is to avoid limite= d with. > Recursive types belong in the same pkg together. Limited with is a kludge= to let=20 > people write JavAda and should never have been added in the 1st place. Hm, interesting assertion. The place I mentioned before is a little FORTH i= nterpreter I was working on ( https://github.com/OneWingedShark/Forth ) so = that Forth.VM (the package containing the VM/interpreter) and Forth.Types (= the package containing the data-types [for cells] and cell-operations) coul= d be mutually dependent: -- Routine is an access to a procedure; this cannot be put into a -- subpool, sadly, and is intended only for definition of words; -- typically, the routines pointed to should have full view of the -- VM (that is the stacks) in order to manipulate them. Type Routine is Access Procedure( State : not null access Forth.VM.Inte= rpreter ); Is that a bad design-choice? If so, why?