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.6 required=5.0 tests=BAYES_00,DATE_IN_PAST_24_48,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,83568e4f0ce7998e
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,UTF8
Received: by 10.66.85.130 with SMTP id h2mr8095220paz.8.1351478344262;
        Sun, 28 Oct 2012 19:39:04 -0700 (PDT)
Path: 
 6ni48364pbd.1!nntp.google.com!border1.nntp.dca.giganews.com!news-in-01.newsfeed.easynews.com!easynews.com!easynews!news-out.octanews.net!mauve.octanews.net!207.246.207.24.MISMATCH!border6.newsrouter.astraweb.com!news.astraweb.com!border6.a.newsrouter.astraweb.com!border4.nntp.ams.giganews.com!border2.nntp.ams.giganews.com!nntp.giganews.com!newsreader4.netcologne.de!news.netcologne.de!news.imp.ch!news.albasani.net!news.mixmin.net!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: Alternative syntax for function definitions?
Date: Sat, 27 Oct 2012 11:02:37 +0200
Organization: Ada @ Home
Message-ID: <op.wmtx2nxkule2fv@cardamome>
References: <op.wmtq0sipule2fv@cardamome>
 <aofcgnli1bud$.1ieeg4tvf6wt0.dlg@40tude.net> <op.wmtun2kuule2fv@cardamome>
 <en1cfkh3booj$.idqhb9xfwi97.dlg@40tude.net>
NNTP-Posting-Host: b7NxRzGgpBNKFlvVWk2OfA.user.speranza.aioe.org
Mime-Version: 1.0
X-Complaints-To: abuse@aioe.org
User-Agent: Opera Mail/12.02 (Linux)
X-Notice: Filtered by postfilter v. 0.8.2
X-Received-Bytes: 2386
X-Original-Bytes: 2243
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: Quoted-Printable
Date: 2012-10-27T11:02:37+02:00
List-Id: <comp.lang.ada>

Le Sat, 27 Oct 2012 10:37:11 +0200, Dmitry A. Kazakov  =

<mailbox@dmitry-kazakov.de> a =C3=A9crit:
> That is no problem. All types should have classes anyway. The dotted
> notation itself is an implementation of some record interface.
To talk about that point, I'm thinking of always using tagged types  =

instead of legacy records, so as to be able to hide or expose the type  =

definition without consequences on the client side, or even just change =
 =

the layout. That's more resilient: if you have three properties A, B, C,=
  =

where one is derived from the two other, say C is derived from A and B, =
 =

and then decide later that instead C will be stored and B derived from A=
  =

and C, you can do that without breaking client, if you use tagged record=
s  =

(you can't with legacy record). But I expect generalisation of use of  =

tagged types to impact efficiency with most compilers (although I'm  =

actually using only one).


-- =

=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