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=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.236.197.39 with SMTP id s27mr1902815yhn.36.1403179720861; Thu, 19 Jun 2014 05:08:40 -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!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!peer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!i13no6284027qae.1!news-out.google.com!a8ni9864qaq.1!nntp.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail NNTP-Posting-Date: Thu, 19 Jun 2014 07:08:40 -0500 Date: Thu, 19 Jun 2014 08:08:40 -0400 From: Peter Chapin User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Ada platforms and pricing, was: Re: a new language, designed for safety ! References: <1402308235.2520.153.camel@pascal.home.net> <85ioo9yukk.fsf@stephe-leake.org> <255b51cd-b23f-4413-805a-9fea3c70d8b2@googlegroups.com> <5ebe316d-cd84-40fb-a983-9f953f205fef@googlegroups.com> <2100734262424129975.133931laguest-archeia.com@nntp.aioe.org> <857442918424729589.090275laguest-archeia.com@nntp.aioe.org> <9j4b774g2gbz$.a22j8j4ai1l1$.dlg@40tude.net> In-Reply-To: <9j4b774g2gbz$.a22j8j4ai1l1$.dlg@40tude.net> Message-ID: X-Usenet-Provider: http://www.giganews.com X-Trace: sv3-soeVsV2AvYmAjch0r1TR5EpEeUL0A05F6T8xO8w2snWr/kj9mC+ys8bHNpI86PitK3tMm+CfjpuVgQY!ybhnjE3/9jKTE/mCgO+Z/aNOd4WmP+9O5KGQCfgcnS5+rk/9CYocC3O8KZSEU5E= X-Complaints-To: abuse@giganews.com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 3245 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Received-Bytes: 3548 X-Received-Body-CRC: 155545189 Xref: news.eternal-september.org comp.lang.ada:20451 Date: 2014-06-19T08:08:40-04:00 List-Id: On 2014-06-19 05:11, Dmitry A. Kazakov wrote: >> Maybe it's a vocabulary issue, but it's not the part where tokens are >> carved out of input text that frighten me, but rather the first level of >> interpretation: what entity is that word referring to? More >> specifically, dealing with use clauses, prefix notations, overloading, >> and stuff like that. > > That looks like sematic analysis to me, when you walk the AST finding > interpretations for each identifier there, prune matched interpretations > for type errors against competing signatures until there is single > interpretation for each, or none, or many conflicting. The most horrific > part is error messages generation. Which requires kind of mind-reading for > programmer's intention. My understand is that parsing Ada requires name resolution to resolve syntactic ambiguities. This means symbol table management and dealing with Ada's visibility rules has to be done while parsing is taking place. This probably depends on precisely how one goes about the parse. Perhaps it is possible to live with the ambiguity and generate a useful parse tree anyway, deferring the rest of the analysis until later, as you say. I'm not sure right now but it is something I'll need to figure out soon. Peter