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!attcan!uunet!trwacs!epstein
From: epstein@trwacs.UUCP (Jeremy Epstein)
Newsgroups: comp.lang.ada
Subject: Re: if UNIX then USE_C ?? (was: Reasons for drop)
Summary: Overloading symbols is not unique to C
Message-ID: <184@trwacs.UUCP>
Date: 27 Feb 90 18:55:08 GMT
References: <27187@cup.portal.com> <18175@megaron.cs.arizona.edu> <5563@crdgw1.crd.ge.com>
Organization: TRW Systems Division, Fairfax VA
List-Id: <comp.lang.ada>

[I promised myself I wouldn't join this grudge match, but...]

In article <5563@crdgw1.crd.ge.com>, kassover@jupiter.crd.ge.com (David Kassover) writes:
> In article <204@puma.ge.com> jnixon@andrew.ATL.GE.COM (John F Nixon) writes:
> Or even worse, I think, is the use of {} for many different kinds
> of block statements.  In Ada I end a loop with end loop;  I end
> an if with end if;

While that's certainly true, look at how Ada overloads symbols.  For
example, parentheses are used for parameters as well as subscripts
(that's something that totally confuses me as an old-time C programmer).
And while we're on the subject of Ada "end", why is it that Ada sometimes
uses "end" to match "begin", and other times to match other keywords?
-- 
Jeremy Epstein
epstein@trwacs.uu.net
TRW Systems Division
703-876-4202