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
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!aioe.org!.POSTED!not-for-mail
From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?=
 =?utf-8?Q?=29?=
 <yannick_duchene@yahoo.fr>
Newsgroups: comp.lang.ada
Subject: Re: Ada platforms and pricing, was: Re: a new language, designed for
 safety !
Date: Fri, 27 Jun 2014 00:44:45 +0200
Organization: Ada @ Home
Message-ID: <op.xh22svonule2fv@cardamome>
References: <1402308235.2520.153.camel@pascal.home.net>
 <ln6uv9$bk8$1@dont-email.me>
 <b22db9fb-a73d-438a-8cfd-f0bb1db70eed@googlegroups.com>
 <MPElv.491358$1w1.428312@fx03.iad>
 <5ebe316d-cd84-40fb-a983-9f953f205fef@googlegroups.com>
 <ln7ngt$c8a$1@dont-email.me>
 <2100734262424129975.133931laguest-archeia.com@nntp.aioe.org>
 <lnn5ko$ner$1@loke.gir.dk> <lnn8ff$k42$1@dont-email.me>
 <857442918424729589.090275laguest-archeia.com@nntp.aioe.org>
 <slrnlq2eom.i0l.lithiumcat@nat.rebma.instinctive.eu>
 <lnrpsq$8ao$1@dont-email.me>
 <slrnlq3jd8.i0l.lithiumcat@nat.rebma.instinctive.eu>
 <erb49jp6qy6n$.5cesca6do7x3$.dlg@40tude.net>
 <slrnlq54jv.i0l.lithiumcat@nat.rebma.instinctive.eu>
 <9j4b774g2gbz$.a22j8j4ai1l1$.dlg@40tude.net>
 <tYmdnRDwdcBVTz_ORVn_vwA@giganews.com> <lnvivr$n8v$1@loke.gir.dk>
 <op.xh1hd4zwule2fv@cardamome> <K41rv.162760$Fd3.161991@fx26.iad>
NNTP-Posting-Host: sL8Mt6L5nmOdbSnd4AdJfA.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: Quoted-Printable
X-Complaints-To: abuse@aioe.org
User-Agent: Opera Mail/12.16 (Linux)
X-Notice: Filtered by postfilter v. 0.8.2
Xref: news.eternal-september.org comp.lang.ada:20624
Date: 2014-06-27T00:44:45+02:00
List-Id: <comp.lang.ada>

Le Fri, 27 Jun 2014 00:24:42 +0200, Shark8 <OneWingedShark@gmail.com> a =
 =

=C3=A9crit:
>> If =E2=80=9Cdefinitely not=E2=80=9D, how do you make =E2=80=9CF(A)=E2=
=80=9D and =E2=80=9CG(A)=E2=80=9D distinct, when F
>> is a sub=E2=80=91program  and G an array? (the most famous example). =
Don't you
>> use name resolution there? Or else do you use an intermediate constru=
ct,
>> like array access temporarily seen as a function? If not this, how?
>
> You don't need to make them distinct, at least not at the  =

> tokenizer-level. Determining what Some_Name(Some_Parameter) is within =
 =

> the realm of the semantic-analysis as Some_Name could refer to: a type=
,  =

> a subprogram, an array... Some_Parameter could be a value or a subtype=
  =

> [if Some_Name is a range-subtype], and all of these permutations are  =

> semantic responsibility rather than syntactic.

I see. I had in mind the syntax described in the RM, as in

     6.4 Subprogram Calls

     unction_call ::=3D
          function_name
        | function_prefix actual_parameter_part

I forget it makes clear `function_name` stands for the token `name`,  =

interpreted as `function_name` and `name` directs to:

     4.1 Names

     name ::=3D
           direct_name | explicit_dereference
         | indexed_component | slice
         | selected_component | attribute_reference
         | type_conversion | function_call
         | character_literal | qualified_expression
         | generalized_reference | generalized_indexing


Yes, indeed, the syntax and its interpretation are well distinguished.

I was misled by some visual memory :P .


-- =

=E2=80=9CSyntactic sugar causes cancer of the semi-colons.=E2=80=9D [1]
=E2=80=9CStructured Programming supports the law of the excluded muddle.=
=E2=80=9D [1]
[1]: Epigrams on Programming =E2=80=94 Alan J. =E2=80=94 P. Yale Univers=
ity