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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,a92e43963a6b930f
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII
Path: 
 g2news1.google.com!postnews.google.com!i31g2000yqm.googlegroups.com!not-for-mail
From: Britt Snodgrass <britt.snodgrass@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: N best things about Ada?
Date: Thu, 8 Jul 2010 18:23:18 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: 
 <e930872d-c38e-4da4-948b-3a2d57509c73@i31g2000yqm.googlegroups.com>
References: 
 <97691fd2-7411-4ccc-bc7b-290aca633cd5@z30g2000prg.googlegroups.com>
NNTP-Posting-Host: 209.252.170.138
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1278638598 12286 127.0.0.1 (9 Jul 2010 01:23:18
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Fri, 9 Jul 2010 01:23:18 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: i31g2000yqm.googlegroups.com; posting-host=209.252.170.138;
	posting-account=rdRzuwoAAAAyW3CSBhs_xgfCUJSc1aNt
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US)
	AppleWebKit/533.4 (KHTML,
 like Gecko) Chrome/5.0.375.99 Safari/533.4,gzip(gfe)
Xref: g2news1.google.com comp.lang.ada:12274
Date: 2010-07-08T18:23:18-07:00
List-Id: <comp.lang.ada>

On Jul 8, 7:52=A0pm, use...@scriptoriumdesigns.com wrote:
> Serious question: =A0What do you consider the N best things / strong
> points / biggest benefits of using Ada? =A0I'm asking as part of my case-
> building for using Ada at work. =A0Of course I have my own list, but I
> don't have anywhere near the Ada experience of most of you folks.
>
> Thanks.

My short list:

 1. Packages as organizational units
 2. Separation of specification from implementation (body)
 3. Subtype ranges
 4. Representation clauses for precise data representation (e.g., for
hardware interfacing)
 5. Case insensitivity (i.e., "case sensitivity considered harmful")
 6. Great readability (e.g., begin/end instead of curly braces)
 7. Underscores allowed in numeric literals (e.g.,
24_3345.7689_3345_8807)
 8. A good (well thought out and reviewed) language standard
 9. The GNAT compiler's great error and warning messages.
10. The availability of SPARK when very high (safe & secure) assurance
is needed.

- Britt