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, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,6327f05d4989a68d X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit X-Received: by 10.180.97.198 with SMTP id ec6mr3425645wib.5.1356186233522; Sat, 22 Dec 2012 06:23:53 -0800 (PST) Path: l12ni188210wiv.1!nntp.google.com!feeder1.cambriumusenet.nl!feed.tweaknews.nl!85.12.40.131.MISMATCH!xlned.com!feeder3.xlned.com!feeder.erje.net!us.feeder.erje.net!gandalf.srv.welterde.de!news.jacob-sparre.dk!hugin.jacob-sparre.dk!nuzba.szn.dk!pnx.dk!news.stack.nl!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Press Release - Ada 2012 Language Standard Approved by ISO Date: Wed, 19 Dec 2012 10:38:03 +0100 Organization: cbb software GmbH Message-ID: <17ldigf63j9c9.qy9f21o7y5ip.dlg@40tude.net> References: <7wrdmbre6jw9.qww9l0uzj6mg.dlg@40tude.net> <50d18248$0$6571$9b4e6d93@newsspool3.arcor-online.net> <50d1872e$0$6567$9b4e6d93@newsspool3.arcor-online.net> Reply-To: mailbox@dmitry-kazakov.de NNTP-Posting-Host: FbOMkhMtVLVmu7IwBnt1tw.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: 40tude_Dialog/2.0.15.1 X-Notice: Filtered by postfilter v. 0.8.2 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Date: 2012-12-19T10:38:03+01:00 List-Id: On Wed, 19 Dec 2012 10:21:51 +0100, Georg Bauhaus wrote: > On 19.12.12 10:19, Dmitry A. Kazakov wrote: >> It is deeply wrong. A [sub]type should describe some class of entities >> sharing common properties and behavior. > > If properties and behavior are functions of physical time, > how does a [sub]type describe the class of corresponding entities? They are not. The whole idea of typing is to abstract/define/describe properties invariant to the program state (and time, and space). They exist before and after the program, and so are independent on whether the program is correct (has bugs), runs, exists. This in turn allows you to design software components independently, to have contracts, to test components before deployment, to verify and validate components. Things that change with time and space are not types. They are called variables, objects etc. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de