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.159.41.69 with SMTP id t63mr39351371uat.8.1481676836774; Tue, 13 Dec 2016 16:53:56 -0800 (PST) X-Received: by 10.157.39.129 with SMTP id c1mr6552231otb.15.1481676836728; Tue, 13 Dec 2016 16:53:56 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.glorb.com!p16no83504qta.1!news-out.google.com!m27ni1257qtf.1!nntp.google.com!p16no83500qta.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 13 Dec 2016 16:53:56 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=67.0.242.189; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC NNTP-Posting-Host: 67.0.242.189 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Ada 2012 Constraints (WRT an Ada IR) From: Shark8 Injection-Date: Wed, 14 Dec 2016 00:53:56 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:32804 Date: 2016-12-13T16:53:56-08:00 List-Id: On Tuesday, December 13, 2016 at 4:19:32 PM UTC-7, Randy Brukardt wrote: > Ada visibility and resolution sadly take all of the fun out=20 > of compiler construction. :-) That's one of the things that I'd like the IR to do; assuming we have a DEP= ENDENCY node (or attribute in the root-node) then it should be possible to = enforce that property so that your problem of "Tags being visible w/o Ada.T= ags being WITH'ed". (This is to say, if we have the dependencies listed, sa= y as a separate Dependency_Type then every entity in the source should have= a 'handle' pointing to an item in the DEPENDENCY attribute xor to a local = construct.) You could then have a "visibility node" (USE) be a sub-tree that has its ow= n handles into the DEPENDENCY attribute and for represents the visibility r= ight in the tree-structure.