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.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,66fae8c862b81b17 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,UTF8 Received: by 10.181.12.101 with SMTP id ep5mr1771606wid.1.1352311584845; Wed, 07 Nov 2012 10:06:24 -0800 (PST) Path: ha8ni161098wib.1!nntp.google.com!feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!ecngs!feeder2.ecngs.de!feeder.erje.net!eu.feeder.erje.net!news2.arglkargh.de!noris.net!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Wed, 07 Nov 2012 19:06:11 +0100 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Copy vector in Ada References: <1aWdnbcg_8-BzAzNnZ2dnUVZ_j6dnZ2d@giganews.com> <6260a796-83c4-4ce5-88cb-8249846bc035@googlegroups.com> <10y91ckm54l57$.8u8bbq342u1b.dlg@40tude.net> <2164bc1a-a841-46ed-bfef-4ddcae4d64f7@googlegroups.com> <1ccf2169-418c-44b7-9d5a-b684a017fbe7@googlegroups.com> <1r3lpzblxy43h$.zytp8ur1bg27$.dlg@40tude.net> <1k3sjasg1wftm$.1vlq5hm7vukhk.dlg@40tude.net> <1sinhhpvja1gx.1ue7br8bz2slq$.dlg@40tude.net> <5098f58c$0$6558$9b4e6d93@newsspool4.arcor-online.net> <509a4dfb$0$6642$9b4e6d93@newsspool2.arcor-online.net> In-Reply-To: X-Enigmail-Version: 1.4.5 Message-ID: <509aa312$0$6634$9b4e6d93@newsspool2.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 07 Nov 2012 19:06:10 CET NNTP-Posting-Host: 4826dd89.newsspool2.arcor-online.net X-Trace: DXC=Vn[VkK_N9Z^@>[RYkFXOIPA9EHlD;3YcR4Fo<]lROoRQ8kFZLh>_cHTX3j]@CKlOnE[>l] X-Complaints-To: usenet-abuse@arcor.de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Date: 2012-11-07T19:06:10+01:00 List-Id: On 07.11.12 17:11, Yannick Duchêne (Hibou57) wrote: > Le Wed, 07 Nov 2012 13:03:08 +0100, Georg Bauhaus > a écrit: > >> On 06.11.12 20:47, Yannick Duchêne (Hibou57) wrote: >>> Now, talking about proper naming of things, how would you explain to a >>> student, that sometime “type” must follow the substitution principle, and >>> sometime, it do exactly the opposite? >> >> The challenge is to explain why the substitution principle is >> a valid commandment: A valuable piece of formal theory, it may >> not offer sufficient justification in the workplace. > > It was never promoted as a commandment in my comments, but said it is not to > be confused to something else, and to be followed when expected, and not > followed when not applicable (like not using it in place of reuse, because > this always gives the illusion of one thing and give another instead). This > find as much justifications as predictability do. > >> Why? Because the workplace is governed by rules that language >> theory/ideology/religion/principles will not normally cover. > > No religion/ideology was spread, but some basic principle recalled. Well, a basic principle about derived types was stated, "a derived type has to cover a base type, and will probably do more, but in anyway, not less", The commandment can be called a basic principle in the light of the substitution principle, but not necessarily in the light of correct algorithms at workplace. To show the absence of issues might be more work. However, if this work makes your algorithm work within specs, the basic principle is at odds with workplace requirements.