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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,fce663eaf40b52f6 X-Google-Attributes: gid103376,public Path: controlnews3.google.com!postnews1.google.com!not-for-mail From: 18k11tm001@sneakemail.com (Russ) Newsgroups: comp.lang.ada Subject: Re: Manifesto against Vector Date: 4 May 2004 22:28:42 -0700 Organization: http://groups.google.com Message-ID: References: NNTP-Posting-Host: 63.194.87.148 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1083734922 6913 127.0.0.1 (5 May 2004 05:28:42 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Wed, 5 May 2004 05:28:42 +0000 (UTC) Xref: controlnews3.google.com comp.lang.ada:262 Date: 2004-05-04T22:28:42-07:00 List-Id: "Marius Amado Alves" wrote in message news:... > > While I agree that Vector is not the best name for this abstraction, I > > have expressed my opinion and the reasons behind it to the ARG during > > earlier discussions of AI-302-03, and the ARG chose Vector. The > > discussion is over. > > It's not over. It was tacitly postponed. I remember that discussion, and > I've just reviewed it. The main argument for "vectors" is that it is widely > used. Well, this argument is simply false. I my 20+ years of programming > languages "array" is clearly the term mostly used. "Vector" is just an > STLism and Java fad. There is additional experience exposed in the > discussion. Incidently, Kopolovich participated, and his arguments are > mostly right. As with all naming issues this one was tacitly postponed then > in favour of design issues. But now the design is done with, and it's time > to perfect naming. A similar thing happened with the indefinite elements > issue. It was once tacitly postponed, with the apparent tendency of *not* to > have them. But then when the more pressing issues cleared, the issue was > brought back, and the position inverted: we now have containers of > indefinite elements in the standard. Compared to this, changing "vectors" to > "arrays" will be a breeze. That said... Some of you may recall that I am an aerospace engineer rather than a software engineer. My objection the the name "vector" is that it has a specific meaning in science and engineering, and its not an unbounded array. A vector is a physical quantity with an direction and a magnitude. Force and velocity are vectors, for example. In state estimation and control theory, a "state vector" is a list of scalars and/or vectors that could include such things as position, velocity, attitude, etc. It is manipulated according to the rules of "Linear Algebra," an amazingly complex and useful branch of mathematics that deals with vectors and matrices. When I first heard about C++ STL "vectors," I was a bit puzzled as to why they chose to override such a common and useful name. I agree with the original poster that Ada should not repeat the mistake. By the way, where do we stand on "with/use"? Ada needs it, and I hope you guys aren't fumbling the ball on that!