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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,635cd9622b25ae59
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news4.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!npeer.de.kpn-eurorings.net!newsfeed.arcor.de!news.arcor.de!not-for-mail
Newsgroups: comp.lang.ada
Subject: Re: Type safety, C++ and code generation
From: Georg Bauhaus <bauhaus@futureapps.de>
In-Reply-To: <e2sark$65f$1@sunnews.cern.ch>
References: <e2q6p8$idj$1@sunnews.cern.ch>
	 <1146143954.169807.207080@t31g2000cwb.googlegroups.com>
	 <e2qj9l$edt$1@sunnews.cern.ch>
	 <1146148380.102042.119860@y43g2000cwc.googlegroups.com>
	 <e2qn8t$n13$1@sunnews.cern.ch>
	 <445101bf$0$11061$9b4e6d93@newsread4.arcor-online.net>
	 <e2sark$65f$1@sunnews.cern.ch>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: #
Message-ID: <1146226568.9048.7.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.1 
Date: Fri, 28 Apr 2006 14:16:08 +0200
NNTP-Posting-Date: 28 Apr 2006 14:15:38 MEST
NNTP-Posting-Host: 7308e693.newsread2.arcor-online.net
X-Trace: 
 DXC=9Q24MghGEX^\ODPOkW97AZQ5U85hF6f;TjW\KbG]kaMX[NGU2GAcMGZ]aHJc1B;;oX=0F65HQV8iVe8Od<X?jRM[
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news2.google.com comp.lang.ada:3982
Date: 2006-04-28T14:15:38+02:00
List-Id: <comp.lang.ada>

On Fri, 2006-04-28 at 07:57 +0200, Maciej Sobczak wrote:


> >    function "*"(a, b: SPEED) return SPEED is abstract;

> I like it, although there is some potential problem with this approach. 
> It uses the "negative logic"

Yes, there is negative logic, which invites mistakes.

And probably this isn't going to be changed, because language
designers somehow seem to think that they must provider what
they think are the usual arithmetic operations. Strangely,
they don't count actual uses, or invent mathematical structures
that reflect computing reality in a field.
How many times does "/" occur in your average computer 
program?
Irrational traditionalism in computer science, school kid's
math habits, or faulty ritual?