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: f5d71,d275ffeffdf83655
X-Google-Attributes: gidf5d71,public
X-Google-Thread: 103376,d275ffeffdf83655
X-Google-Attributes: gid103376,public
X-Google-Thread: 109fba,d275ffeffdf83655
X-Google-Attributes: gid109fba,public
X-Google-Thread: 146b77,d275ffeffdf83655
X-Google-Attributes: gid146b77,public
From: dennison@telepath.com
Subject: Re: Ada vs C++ vs Java
Date: 1999/01/20
Message-ID: <784qvi$a0a$1@nnrp1.dejanews.com>#1/1
X-Deja-AN: 434804760
References: <369C1F31.AE5AF7EF@concentric.net>
 <tz5n2.4608$TO5.129375@ptah.visi.com> <369DDDC3.FDE09999@sea.ericsson.se>
 <369e309a.32671759@news.demon.co.uk> <369F1D39.64A65BC1@sea.ericsson.se>
 <369f81a9.31040093@news.demon.co.uk> <77ommt$9bo$1@nnrp1.dejanews.com>
 <77vhjf$nn9$1@nnrp1.dejanews.com> <77vld9$qvg$1@nnrp1.dejanews.com>
 <YkGBP4MNXb2t-pn2-bjzMwxf6POdh@localhost> <782rp0$kn6$1@nnrp1.dejanews.com>
 <6Oap2.16170$MW1.4028@news2.giganews.com> <783nnb$s9c@drn.newsguy.com>
X-Http-Proxy: 1.0 x5.dejanews.com:80 (Squid/1.1.22) for client 204.48.27.130
Organization: Deja News - The Leader in Internet Discussion
X-Article-Creation-Date: Wed Jan 20 14:59:05 1999 GMT
Newsgroups: comp.lang.c++,comp.vxworks,comp.lang.java,comp.lang.ada
X-Http-User-Agent: Mozilla/4.5 [en] (WinNT; I)
Date: 1999-01-20T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <783nnb$s9c@drn.newsguy.com>,
  bill@nospam.com wrote:

> btw, since Ada has no braces, what is the problem? this only seems to
> be C/C++/Java thing, since those uses braces.

The braces are really just a cryptic shorthand for "begin" and "end", which
Ada does have.

A good example of an Ada syntax spat is listing procedure parameters in
function bodies. Say I have a fuction w/ 2 input parameters. Here are a few
of the ways I have seen that written out.

(1)
function foo (Left : in Integer; Right : in Float) return Boolean is
begin
   ...
end foo;

(2)
function foo (Left  : in Integer;
              Right : in Float) return Boolean is
begin
   ...
end foo;

(3)
function foo
  (Left  : in Integer;
   Right : in Float) return Boolean is

(4)
function foo
  (Left  : in Integer;
   Right : in Float
  ) return Boolean is

(5)
function foo
  ( Left  : in Integer
  ; Right : in Float
  ) return Boolean is

(6)
function foo (Left  : in Integer;
              Right : in Float)
  return Boolean
is
begin

...I could go on and on. And of course Ada "style guides" will typically
require one and only one of these formats to be used. A sensible programmer
would switch from style (1) or (2) when they run out of space on the line to
something like style (3) or (4). Remember that Ada developers tend to use
fairly long identifier names, so this can easily happen. But if the style
guide doesn't give you that lattitude, you might be forced to stick with the
other style but make one of the lines wrap to the next line. That's much
tougher to read. More typically the style guide gets ignored because
following it would be counter-productive. But that's an awfully slippery
slope...

T.E.D.

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own