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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,c58a5b8372dc24a0
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news2.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nntp.club.cc.cmu.edu!feeder.erje.net!eternal-september.org!.POSTED!not-for-mail
From: BrianG <briang000@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: confusion with string initialization
Date: Wed, 28 Apr 2010 09:26:26 -0400
Organization: A noiseless patient Spider
Message-ID: <hran85$ot2$3@news.eternal-september.org>
References: <ZpWdnRumIodDKFTWnZ2dnUVZ_tudnZ2d@giganews.com>
	<HcCdnUYotp1F91fWnZ2dnUVZ_gmdnZ2d@giganews.com>
	<alpine.LNX.2.00.1004191451020.16262@Bluewhite64.example.net>
	<hqhod3$tit$1@news.eternal-september.org>
 <874oixmfe3.fsf@hugsarin.sparre-andersen.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 29 Apr 2010 01:26:30 +0000 (UTC)
Injection-Info: mx02.eternal-september.org;
 posting-host="yhQWPMeVRpVpuDNdNP0zCg";
	logging-data="25506"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX18MFrqGz4v3u5GY606+CqYE"
User-Agent: Thunderbird 2.0.0.24 (X11/20100317)
In-Reply-To: <874oixmfe3.fsf@hugsarin.sparre-andersen.dk>
Cancel-Lock: sha1:jQzrogx7ASHTZatKlfAdSWYTSSI=
X-Original-Bytes: 2095
Xref: g2news2.google.com comp.lang.ada:11245
Date: 2010-04-28T09:26:26-04:00
List-Id: <comp.lang.ada>

Jacob Sparre Andersen wrote:
> J-P. Rosen wrote:
...
>> Because it makes lisibility a lot better by drawing attention of the
>> reader on what actually the thing does, and getting rid of useless
>> information that you can find easily by clicking on the identifier and
>> selecting "go to declaration".
>>
...
> 
> But simply referring the students to a "go to declaration" feature in
> their editors might also be a solution, once the code is in an editor.
> 

And (depending on the editor) once it has been compiled, or even is able 
to be compiled.

A middle ground might be to limit yourself to a single use - then you 
know where something is from, if it's not obvious.

Personally, I prefer a renames if I want to declutter the code (once 
you've reached that, if you're teaching).

--Brian