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.8 required=5.0 tests=BAYES_00,INVALID_DATE,
	MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!crdgw1!control!kassover
From: kassover@control.crd.ge.com (David Kassover)
Newsgroups: comp.lang.ada
Subject: Re: if UNIX then USE_C ?? (was: Reasons for drop)
Message-ID: <5575@crdgw1.crd.ge.com>
Date: 26 Feb 90 22:00:19 GMT
References: <27187@cup.portal.com> <18175@megaron.cs.arizona.edu> <5476@crdgw1.crd.ge.com> <34196@news.Think.COM> <5518@crdgw1.crd.ge.com> <204@puma.ge.com> <5563@crdgw1.crd.ge.com> <209@puma.ge.com>
Sender: news@crdgw1.crd.ge.com
Organization: Aule-Tek, Inc.
List-Id: <comp.lang.ada>

In article <209@puma.ge.com> jnixon@andrew.ATL.GE.COM (John F Nixon) writes:
>It is possible to make single character mistakes in Ada.
...

 I thought I said that.  I thought I gave an example analogous to
yours, involving quantites declared by the programmer with one
character differences.

We often do this kind of thing because we don't want to type
stuff like in COBOL programs where everything with less than 3
_'s is a reserved word.
 
It's difficult to avoid when it is necessary to type an explicit
index into an array, so as to specifically distinguish x(1) from
x(2).

(it is impractical to avoid *all* litterals)

My personal preference for Ada over C has to do with the fact
that when I must write (or FIX) a program, the less time I spend
avoiding traps rather than doing my work, the better.

Also, personally, I have a hard time reading one-line wonders,
especially other people's.  It's harder to create such in Ada,
therefore I see less of them.