From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org  Mon Oct 26 17:06:54 2020
Return-Path: <owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org>
X-Original-To: sc22wg5-dom9
Delivered-To: sc22wg5-dom9@www.open-std.org
Received: by www.open-std.org (Postfix, from userid 521)
	id E646D3588A5; Mon, 26 Oct 2020 17:06:54 +0100 (CET)
Delivered-To: sc22wg5@open-std.org
Received: from mr85p00im-zteg06021501.me.com (mr85p00im-zteg06021501.me.com [17.58.23.183])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by www.open-std.org (Postfix) with ESMTP id 6B82F356699
	for <sc22wg5@open-std.org>; Mon, 26 Oct 2020 17:06:53 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com;
	s=1a1hai; t=1603728411;
	bh=nlq6lGI/H8oa8W/ij3rYWLqcz+kO1qjsnRHrrKemIlU=;
	h=From:Content-Type:Mime-Version:Subject:Message-Id:To:Date;
	b=nHAvrvJ7fOFDV1mlRQbIbV1fuXv3t/9jdJpQnVyo5T48G4wls2Wn15tHkj1HmphOM
	 eJVUxVWDYkUYiZPTFqGLhBGXz2tBJuINFTjrQQkhKj70KaDxZoPtOHYPlwG6GTiSoe
	 F7BMJxQ6KFlLBRk6auVSOSoDkwfZHL2Nrc+tKqQoks7TOguD4IO1y2uV2/zyq0571n
	 ZVKRapsx15olpURDDFYSr3ylP9DLwgtUS3apihhivUVNdHG6Gbfpa7MfnGRpiYKZMg
	 cxTIqy5ZtYPtDdvuuGJUtOyZ7aamIqlf43IFCkRe2e58QYIFVJ2cMk/LR4iUPP1g3Z
	 mQ3BWZ1/SFbhg==
Received: from davids-imac.home (host86-143-52-205.range86-143.btcentralplus.com [86.143.52.205])
	by mr85p00im-zteg06021501.me.com (Postfix) with ESMTPSA id 6020A380528
	for <sc22wg5@open-std.org>; Mon, 26 Oct 2020 16:06:51 +0000 (UTC)
From: David Muxworthy <d.muxworthy@icloud.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
Subject: Fwd: BOUNCE sc22wg5@open-std.org:    Non-member submission from [Van
 Snyder <w.van.snyder@gmail.com>]
Message-Id: <2BD6BCA5-C483-4EF3-A9D6-7E0868DE05AC@icloud.com>
References: <20201022213516.6E247358ABA@www.open-std.org>
To: sc22wg5@open-std.org
Date: Mon, 26 Oct 2020 16:06:48 +0000
X-Mailer: Apple Mail (2.3445.9.7)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235,18.0.737
 definitions=2020-10-26_08:2020-10-26,2020-10-26 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=15 malwarescore=0
 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0
 mlxlogscore=578 adultscore=0 classifier=spam adjust=0 reason=mlx
 scancount=1 engine=8.0.1-2006250000 definitions=main-2010260110
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

=46rom owner-sc22wg5@www.open-std.org  Thu Oct 22 23:35:16 2020
Return-Path: <owner-sc22wg5@www.open-std.org>
Delivered-To: sc22wg5@open-std.org
Received: from mail-pg1-f171.google.com (mail-pg1-f171.google.com =
[209.85.215.171])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by www.open-std.org (Postfix) with ESMTP id E29E2358628
	for <sc22wg5@open-std.org>; Thu, 22 Oct 2020 23:35:15 +0200 =
(CEST)
Received: by mail-pg1-f171.google.com with SMTP id o7so1815252pgv.6
       for <sc22wg5@open-std.org>; Thu, 22 Oct 2020 14:35:15 -0700 (PDT)
DKIM-Signature: v=3D1; a=3Drsa-sha256; c=3Drelaxed/relaxed;
       d=3Dgmail.com; s=3D20161025;
       =
h=3Dmessage-id:subject:from:to:date:references:user-agent:mime-version;
       bh=3DbfkqiDQ3I+J7nOpg40/4a+QIg9X6sjQGhIGvtb2ubpo=3D;
       =
b=3DhpgMZ6yRU8Hyeo7WKiREx1yQI2La5IIvBl4dL/gzZddn1tbzWykkgAN8Y+WSyQ4+HE
        =
wnLKZqtLNayz9Lv7is8tROCSCN0KfSD3WcBoJ2kXatH65ftB3vcP58+u0lWbEkiIJLaj
        =
kjQRw7z2yYW0oe93w8PBU7r8FmYVHe9o21HSMS5EZfCGagT7CvYWJrFFICU3Lh5UDGBA
        =
SlEXdR0HcMZc2XiVHIH4Ziz0Kd9SNy60FkJTT/S636RvDJY0mlwhC0h0Acvlj96rTNDv
        =
1wyozUXtMFjrspbIHTt82u7tuMth9ZB6mFsnAvuVha/1wc6nW0W15RONPhm4wLYD9fYC
        eJCw=3D=3D
X-Google-DKIM-Signature: v=3D1; a=3Drsa-sha256; c=3Drelaxed/relaxed;
       d=3D1e100.net; s=3D20161025;
       h=3Dx-gm-message-state:message-id:subject:from:to:date:references
        :user-agent:mime-version;
       bh=3DbfkqiDQ3I+J7nOpg40/4a+QIg9X6sjQGhIGvtb2ubpo=3D;
       =
b=3DHZBkLq73J0BTUFFwgrNvajmRo+8Nf0Uf5jvA5NWZK2hkjWbUUOHGsH7Z0v+cymdHB2
        =
VdiWBzrjNshz/SQQewehFPV83M60kBJPHNyOm/qOWBpLcaxo63ZzxiD/xvIIFc0okX6Q
        =
IugW6BYwNpIA0sk/ob4somjr+VZDwjNLjW+16r7qTB3pdA0Wed5+efE4fQaGZbmh8JxC
        =
PXJt9+nudLiPGippSqzr+dQDYRugQWM8S0mYDv7m/18bg1Sz2J986qAZhHxugyxJD4Co
        =
otC2UiZDXk1b7mhm+MzoJhIWsHt0Esa5mRKZ8cCu+6Z+0j9dFe5iObz/UURF3br5pYdr
        EaxA=3D=3D
X-Gm-Message-State: =
AOAM533dTkt9qgg8JNcS68+l1eUeq4ByZwNvhURrWbtE88Dtqh11bt73
	+fnW5t0M7Id0fSIAbHBqop2wKruNWUFPmg=3D=3D
X-Google-Smtp-Source: =
ABdhPJwBBvf7rtqYcRWkrxDIPOeexBij/1VqC8Rr9gyfcZcW45+S53ffxFkzqYB8fcjir3C9jr=
2p9Q=3D=3D
X-Received: by 2002:a17:90a:7c0c:: with SMTP id =
v12mr4024165pjf.71.1603402513498;
       Thu, 22 Oct 2020 14:35:13 -0700 (PDT)
Received: from van.vsnyder (047-229-011-079.res.spectrum.com. =
[47.229.11.79])
       by smtp.gmail.com with ESMTPSA id =
ck21sm2920793pjb.56.2020.10.22.14.35.12
       for <sc22wg5@open-std.org>
       (version=3DTLS1_3 cipher=3DTLS_AES_256_GCM_SHA384 bits=3D256/256);
       Thu, 22 Oct 2020 14:35:12 -0700 (PDT)
Message-ID: <ea4c8f7d414782b0acfcd892260b84645c20a67a.camel@gmail.com>
Subject: [Fwd: [ARG] Importance of "cosmetic" changes]
From: Van Snyder <w.van.snyder@gmail.com>
To: sc22wg5 <sc22wg5@open-std.org>
Date: Thu, 22 Oct 2020 14:35:12 -0700
References: <6DF79AED-4B71-4985-B84A-37D7A08687D3@adacore.com>
Content-Type: multipart/alternative; boundary=3D"=3D-gEm4FOosm1ann59uxqHI"=

User-Agent: Evolution 3.30.5-1.1=20
MIME-Version: 1.0


--=3D-gEm4FOosm1ann59uxqHI
Content-Type: text/plain; charset=3D"UTF-8"
Content-Transfer-Encoding: 7bit

I got this message from the Ada Rapporteur Group. It's a reasonable
view for any standard.

Van

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D=3D

Bob Duff mentioned that he was against wasting a lot of time making
"cosmetic" changes to the RM, and for that reason voted against AI12-
0399-1.  I sympathize with this view, but on balance I think such
"cosmetic" changes are actually pretty important in the long run.

I believe there is an analogy with making changes to a house -- an
architect friend told me that when he designed an extension to a house,
one of the goals was that when someone entered the house when it was
done, if they hadn't seen the house before, they couldn't tell what was
the old part and what was the new part.

I feel the same general goal should apply to a good language update.=20
If you haven't seen a prior version, then when you look at the
reference manual for the extended language, you shouldn't be able to
tell what are the old features and what are the new features.  One
difference for Ada -- when we want to remove something, we actually
move it into Annex J (effectively the dusty old "attic" of the
language) rather than just putting it into a dumpster.

Perhaps more importantly, a new user of Ada need not be aware of what
parts of the language are brand new, and what parts have been there
since the beginning.  If they have an historical bent, they could look
in Annex J, but as a new user they should probably completely ignore
it.

So I think the cosmetic changes ultimately simplify the process of
understanding the reference manual, by making it more consistent, with
the same idioms used in similar contexts.

Your mileage may of course vary...

-Tuck


--=3D-gEm4FOosm1ann59uxqHI
Content-Type: text/html; charset=3D"utf-8"
Content-Transfer-Encoding: quoted-printable

<html dir=3D3D"ltr"><head></head><body style=3D3D"text-align:left; =
direction:lt=3D
r;"><div>I got this message from the Ada Rapporteur Group. It's a =
reasonabl=3D
e view for any =
standard.</div><div><br></div><div>Van</div><div><br></div><=3D
=
div>=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=
=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D
=
=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3=
D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D
=
=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3=
D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D
=3D3D=3D3D=3D3D</div><div><br></div><div>Bob Duff mentioned that he was =
against w=3D
asting a lot of time making "cosmetic" changes to the RM, and for that =
reas=3D
on voted against AI12-0399-1.  I sympathize with this view, but on =
balance =3D
I think such "cosmetic" changes are actually pretty important in the =
long r=3D
un.</div><div><br></div><div>I believe there is an analogy with making =
chan=3D
ges to a house -- an architect friend told me that when he designed an =
exte=3D
nsion to a house, one of the goals was that when someone entered the =
house =3D
when it was done, if they hadn't seen the house before, they couldn't =
tell =3D
what was the old part and what was the new =
part.</div><div><br></div><div>I=3D
feel the same general goal should apply to a good language update.  If =
you=3D
haven't seen a prior version, then when you look at the reference manual =
f=3D
or the extended language, you shouldn't be able to tell what are the old =
fe=3D
atures and what are the new features.  One difference for Ada -- when we =
wa=3D
nt to remove something, we actually move it into Annex J (effectively =
the d=3D
usty old "attic" of the language) rather than just putting it into a =
dumpst=3D
er.</div><div><br></div><div>Perhaps more importantly, a new user of Ada =
ne=3D
ed not be aware of what parts of the language are brand new, and what =
parts=3D
have been there since the beginning.  If they have an historical bent, =
the=3D
y could look in Annex J, but as a new user they should probably =
completely =3D
ignore it.</div><div><br></div><div>So I think the cosmetic changes =
ultimat=3D
ely simplify the process of understanding the reference manual, by =
making i=3D
t more consistent, with the same idioms used in similar =
contexts.</div><div=3D
> <br></div><div>Your mileage may of course =
vary...</div><div><br></div><pre=3D
> -Tuck</pre><pre><br></pre></body></html>

--=3D-gEm4FOosm1ann59uxqHI--


