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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,2a993df02f6d82f1 X-Google-Attributes: gid103376,public From: Samuel Mize Subject: Re: More questions... Date: 1999/03/09 Message-ID: <7c42du$27m5@news1.newsguy.com>#1/1 X-Deja-AN: 453133657 References: <7bvb4j$lt0$1@remarQ.com> Organization: ImagiNet Communications, Ltd. User-Agent: tin/pre-1.4-981002 ("Phobia") (UNIX) (AIX/3-2) Newsgroups: comp.lang.ada Date: 1999-03-09T00:00:00+00:00 List-Id: Michael Young wrote: > 1) I've heard it said here that Ada, compared to other languages, is > "reader-friendly" at the expense of being "writer-unfriendly". I > understand the need to be reader friendly. I'm curious why you feel it > is friendlier to read than, say, C++. This is more a touchstone for comparing possible language constructs to put into Ada, than a touchstone for comparing Ada to other languages. And I'm not sure that "friendly" is the most accurate term for it. That's a subjective judgement, and some people find while (*a++=*b++); to be "friendlier" than the Ada equivalent. I'd say that the idea is that the reader's first impression of the code should be both unambiguous and correct. One element is explicitness over conciseness. For instance, in Ada, you can freely convert between separate integer types, just as you can in C (and I assume in C++). However, you have to explicitly state that you are doing so. Aside from detecting typos (and thinkos), this tells the later code reader that you really did intend to do that. Best, Sam Mize -- Samuel Mize -- smize@imagin.net (home email) -- Team Ada Fight Spam: see http://www.cauce.org/ \\\ Smert Spamonam