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-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,5cb36983754f64da
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2004-04-05 11:08:18 PST
Path: 
 archiver1.google.com!news2.google.com!fu-berlin.de!uni-berlin.de!sdn-ap-012tnnashp0163.dialsprint.NET!not-for-mail
From: "Marc A. Criley" <mcNOSPAM@mckae.com>
Newsgroups: comp.lang.ada
Subject: Re: No call for Ada
Date: Mon, 5 Apr 2004 13:07:52 -0500
Message-ID: <c4s7af$2kdngp$1@ID-218515.news.uni-berlin.de>
References: <20040206174017.7E84F4C4114@lovelace.ada-france.org>
 <mailman.3.1076142690.295.comp.lang.ada@ada-france.org>
 <m3isij11u4.fsf_-_@insalien.org>
 <54759e7e.0402071124.322ea376@posting.google.com>
 <m3smhmz2fo.fsf@insalien.org> <rxmbc.53$bh.32@lakeread02>
 <pan.2004.04.02.23.55.20.921881@email.ro> <87r7v5zao0.fsf@insalien.org>
 <6803831.c4KqqVc08g@linux1.krischik.com> <87vfkgy9z6.fsf@insalien.org>
 <87zn9sjc5r.fsf@deneb.enyo.de>
NNTP-Posting-Host: sdn-ap-012tnnashp0163.dialsprint.net (63.189.240.163)
X-Trace: news.uni-berlin.de 1081188496 88530457 I 63.189.240.163 ([218515])
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Xref: archiver1.google.com comp.lang.ada:6752
Date: 2004-04-05T13:07:52-05:00
List-Id: <comp.lang.ada>


"Florian Weimer" <fw@deneb.enyo.de> wrote in message
news:87zn9sjc5r.fsf@deneb.enyo.de...
> Ludovic Brenta <ludovic.brenta@insalien.org> writes:
>
> > Is this not a strength rather than a weakness?  Garbage collectors
> > encourage sloppy programming.
>
> So does Ada's type safety.

Pardon??

There are only a couple ways I can think of wherevone could conceivably
argue that type safety encouraged sloppy programming:

One way is if the programmer is just going to churn out code and then
compile it again and again and again ad nauseum while the compiler
identifies all the type conflicts after the fact. And the fixing of which
basically means going back and declaring types and variables intelligently,
which would've been much less exasperating to do at the start.

Or, due to the presence of Ada's type safety, the programmer wants to
_avoid_ it, and so declares all numeric variables to be of the standard
types integer and float.

It's in dynamically typed languages where I've seen sloppy programming as
regards variable typing.

Marc A. Criley