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=-0.3 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,38fc011071df5a27
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-06-17 09:58:56 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!small1.nntp.aus1.giganews.com!border1.nntp.aus1.giganews.com!intern1.nntp.aus1.giganews.com!nntp.giganews.com!nntp.gbronline.com!news.gbronline.com.POSTED!not-for-mail
NNTP-Posting-Date: Tue, 17 Jun 2003 11:58:54 -0500
Date: Tue, 17 Jun 2003 11:59:37 -0500
From: Wesley Groleau <wesgroleau@despammed.com>
Reply-To: wesgroleau@despammed.com
Organization: Ain't no organization here!
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
 rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en, es-mx, pt-br, fr-ca
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Ideas for Ada 200X "left hand side" repeater.
References: <slrnbebc2b.ht.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <bebbba07.0306101640.19178e81@posting.google.com>
 <3EE7CC70.E1FD3A67@adaworks.com>
 <bebbba07.0306121116.33e4741@posting.google.com>
 <bcbu9i$hgu5j$1@ID-175126.news.dfncis.de> <AwvGa.1228118$F1.143267@sccrnsc04>
 <3EECA772.4B662024@adaworks.com> <hYmHa.6881$Hb.124073@news4.e.nsc.no>
 <BB13C10D.350A%yaldnifw@blueyonder.co.uk>
 <bcl1pu$jscm4$1@ID-175126.news.dfncis.de>
 <BB13CDB9.3516%yaldnifw@blueyonder.co.uk>
 <bcl4o8$kkj68$1@ID-175126.news.dfncis.de>
 <eIydnQ7dD_77h3OjXTWJiA@gbronline.com> <bclnfn$1ga0$1@msunews.cl.msu.edu>
 <BB14B31A.35B6%yaldnifw@blueyonder.co.uk>
 <BB14D345.35C8%yaldnifw@blueyonder.co.uk>
 <slrnbeu6cp.clr.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <BB14D999.35D3%yaldnifw@blueyonder.co.uk>
 <slrnbeu7ft.d0u.randhol+abuse@kiuk0152.chembio.ntnu.no>
In-Reply-To: <slrnbeu7ft.d0u.randhol+abuse@kiuk0152.chembio.ntnu.no>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <e_GdnRh0ovFS1XKjXTWJkg@gbronline.com>
NNTP-Posting-Host: 216.117.18.41
X-Trace: 
 sv3-0h5kqp/8yL3SbpdUtW+9kn5clsWsJqsYm4AOl32Run60EntWVYeTO3z4UqUeO0r882Ablj9rdYYwdHO!6126L75/q6d+qaCJAuy1uJuWZDi1UNR8RNZZW/v+DWu/xYLkVPMQLlRaB/wsOTRH7tGub1ozOIh9!h7eU
X-Complaints-To: abuse@gbronline.com
X-DMCA-Complaints-To: abuse@gbronline.com
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.1
Xref: archiver1.google.com comp.lang.ada:39348
Date: 2003-06-17T11:59:37-05:00
List-Id: <comp.lang.ada>


> If one use "is" I would have thought :
> 
>    Screen.Buffer(i) is Pixel in Pixel := Pixel + 1;
> 
> but perhaps this is because of that Norwegian is my language and English
> only the second?

Actually, if one wants to emulate English,

    Pixel is Screen.Buffer(i) in Pixel := Pixel + 1;

would be semantically better.

But it seems to me that renames covers all the "wishes"
so far except two.  And it adds two:

1. With a declare block, one can give the new name as big
    or as small a scope as needed.

2. The new name can be something that logically suits
    the scope it's given.

The two that are not covered:

1. The wish to trim the number of keystrokes to
    an absolute minimum.  As most of us know, that
    is NOT a concern of an Ada fan.

2. The wish to avoid temporaries for a more efficient
    construct.  As has already been said more than once,
    this is a red herring.  It can avoid temporaries
    ONLY if doing so would not break any other language
    rules.  And there is (obviously) no language rule
    requiring the current construct to be less efficient
    than the new one.

3. One point in favor of the new construct is that if
    evaluation had side effects, they would occur once
    instead of twice.  But in that case, instead of
    renames, one would use an initialized variable
    (and copy-back or write-through) or an in out parameter.