Talk:Ada (programming language)

This is an old revision of this page, as edited by Krischik (talk | contribs) at 14:55, 30 November 2004 (correct lines - should not be :----). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Ada Home

  • Ada Home - Old Web Site for Ada (not maintained)
I agree it is not maintained, but it is still used by Ada practitioners for reference. It is still recently referenced from the comp.lang.ada group. So I have restored the extlink. -Wikibob | Talk 11:24, 2004 Jun 16 (UTC)

Moved comments

Moved comments here from main text. Reorganized into threads.--buzco

Ariane 5

The descrition of the Ariane 5 Failure should not be on a side discribing a programming lanuage a link to a different side should be enough. Ariane 5 Failure

Hermann Wacker

US Department of Defense

Really only used anymore in US Department of Defense stuff. Oh yeah, and Ada95, the most popular Ada compiler actually translates your code to C, then compiles the C. I love that.


Ada95 is not a compiler, it is a version of Ada, the most recent version, I believe. I am also skeptical of the idea that Ada is "really only used anymore" in the US DOD.

Do you mean GNAT (GNU Ada Translater) when writing "Ada95"? This is no translater to C any longer but a frontend to the GNU Compiler Collection, as the C or the Java frontends are. By the way, it is _not_ used only by DOD staff and it is a highly capable language. In contrast to the popular misbelief it produces rather fast code (comparable to C).

Make that C, C++, Forth, FORTRAN, Java, Objective C and Pascal front ends! May be others! --buzco

The team behind Gnat used in the beginning a proprietary Ada compiler and used that to build an compiler which implemented a subset of Ada big enough to support building itself. Now the team left that proprietary compiler in the dust. After that it was a simple matter of extending that they already have while using the base to build the next more evolved version.
Gnat until 3.11 or so (ca 1999) needed to generate a C stub for the sake of elaboration but that liability is no more !!
GNAT never was a Ada-to-C translator !
cfront was a c++-to-c translator !

theory books

Ada is used in a few compiler theory books because of its comprehensiveness and elegance.

primary users

Should there be a section on primary users of a language like ada and how their requirements affected the language?

Pascal

Ada has some tastes of Pascal still but not one of the bad ones. --Janet Davis

list of possible topics

(list of possible topics moved from main page) What about

  • how Ada tied into formal specification languages?
  • how Ada is very stongly typed
  • packages in Ada
  • concurrency support
  • real time/embedded system support ???
  • how Ada suffered from design by DOC committee/specifications and required super-fast hardware for compilation/debugging.
  • ?? others

list of possible topics

I think the Steelman language requirements page would be better as part of this entry, or maybe a subpage, as it isn't really of interest except in the context of Ada. Anyone agree/disagree? --Matthew Woodcraft

More Ariane 5

I don't think the note re the Ariane 5 disaster is quite correct. As I understand it, the fault was the re-use of a part and its software, which had worked properly on the Ariane 4. However, the more powerful engines on the Ariane 5 gave a thrust/velocity/displacement that was out of the part's design range, and the part detected that fact -- correctly, according to its original design. But since it thought it had a number that failed the sanity check it went into debug mode -- again according to design -- and started dumping debug data onto the rocket's control bus. So unless my understanding of the problem is wrong, the problem was a simple failure to review a part's specifications, and nothing at all to do with the programming language or compilation switches. -- B.Bryant

That's basically my understanding of the situation, except that 'detected that fact' is a bit strong -- it seems that the error was a CPU-level floating point trap, with no high-level-language handler. The Ada task in question didn't actually do anything useful after takeoff, so if the exception hadn't been explicitly suppressed the rocket would have been safe.
Certainly that bit of the article could do with improvement, but some mention is probably appropriate in this article (if it were taken out someone would just add it in again). -- Matthew Woodcraft

Re: "design by DOC committee

Ada was not "designed by committee", each version (Ada and Ada-95) had ONE designer that had final say on any feature or change to the language. Its design is far cleaner and more organized than many other languages. -- RTC 01:38 2 Jul 2003 (UTC)
True. The DOD's choice of Ada was the result of a competitive tendering process in which Ada beat the other contenders. The only role of a committee was to decide that it was better than the other proposed languages. -- Derek Ross

Re: "required super-fast hardware for compilation/debugging"

I added a section on the problems that the early compilers had and why. -- RTC 02:16 2 Jul 2003 (UTC)
Hmm, I never heard about Ada 80 and I discussed with lots of people involved in early Ada including Jean Ichbiah and people from the Ada/Ed project (first validated Ada compiler). Would you mind naming exactly the documents and compilers? Also point to document about elaboration issues? Thanks. Guerby 21:20 17 Jul 2003 (UTC)
I took the liberty of removing that entire section, not only because of Guerby's concerns, but because a quick search of the Web shows that the Ada Mandate was not signed into law until 1990, so it cannot be blamed for the quality of 1980-era compilers.
FWIW I have also heard mention that when Ada first came out it demanded things beyond then-current compiler technology, so maybe there is still a need for a section like the one I removed. However, if anyone decides to put such a section back in, please check and document any claims of fact included in the section. - B.Bryant 23:40 21 Jul 2003 (UTC)

Silly criticisms

Ada was widely called by many the "language of the future", but has never been used that much outside of the government. This title is often laughed at by programmers now. A major impediment to Ada's widespread adoption may have been that it is extremely verbose and the variable name conventions (requiring CamelCase and underscores to be used in the same variable name, such as This_Variable) are difficult to type, look ugly, and don't provide any information, unlike variable name conventions for just about every other language do.

I'm excising this whole paragraph. I've never heard it called the "language of the future", after reading a lot about Ada. For every language, you can find someone hyping it that looks silly in retrospect. Usage may be important, but it needs a lot more than just "never been used that much". "The variable name conventions ... are difficult to type, look ugly, and don't provide any information, unlike variable name conventions for just about every other language do" is a bit absurd; Ada has the same freeform variable names that most modern languages do, and the names I've seen in C code look much like the ones in Ada. To say that other language name conventions aren't difficult to type and don't look ugly is a very arguable case to make; BASIC and FORTRAN's short variable names, FORTRAN's type-name relations and Perl's type-name relations can be considered ugly and difficult.

I'd like to see some valid criticisms on Ada, but these are just silly. --Prosfilaes 02:19, 1 Jul 2004 (UTC)

date discrepancy?

In May of 1979, the Green proposal, designed by Jean Ichbiah at Cii Honeywell Bull, was chosen and given the name Ada

the above is chronologically the first mention of the name 'Ada' being associated with the Ada programming language. I'm quite certain that when I worked for the US Navy, and at sometime definitely prior to 1976 June 13, that I heard mention of 'the Ada Project' more than once. Do we have any info available from nonclassified source about this beingcalled the Ada Project, prior to 1979?

Reversion of Sep. 14th changes

There was nothing awful, but nothing great. Ada83 is one version of Ada, not another name for; "statically typed" is more unambigious than "strongly typed"; it was created to stop the proliferation of languages in the DoD, and improving on other languages (and not just C and C++) was a side-goal; what it was designed to do is important; and tasking is just one feature out of many.


I replaced "Ada was named after Ada, Lady Lovelace, the first computer programmer" with "Ada was named after Ada, Lady Lovelace", because the statement that she was a computer programmer directly contradicts the linked Wikipedia article (as well as other sources). My edit was reverted by UtherSRG with no explanation. I'm not trying to denigrate Ada Lovelace or the Ada language; I'm just trying to correct a factual error in a Wikipedia article. There is no historical evidence to support the common belief that she wrote programs for the Analytical Engine. -- BenRG 00:23, 12 Oct 2004 (UTC)

Sorry Ben. I get a bit overzealous guarding some articles from anonymous editors. You are right, the article on Ada Lovelace indeed points out that she probably didn't do any programming. Take a look again at the sentence in quesiton. - UtherSRG 14:00, 12 Oct 2004 (UTC)
Sure, I'm happy with that. -- BenRG 21:21, 18 Oct 2004 (UTC)


Ada Capitalization

I propose to change the capitalization of the identifier 'Text_Io' in the Hello World! example. In my opinion the correct letter case is 'Text_IO' and not 'Text_Io', as it's found in the Ada Reference Manual and also in the GNAT source code. Although Ada is not case sensitive this doesn't mean that capitalization isn't important. The Ada 95 Quality and Style Guide recommends to 'Use uppercase for abbreviations and acronyms', e.g. Text_IO (for Input/Output). Moreover, GNAT has an option to check attribute casing and reject any identifier that doesn't mach with its definition casing. Both forms are syntactically correct, but Text_IO is more correct and follows the language's guidelines of quality and style. Thanks -- suruena 14:13, 2004 Nov 30 (UTC)

Right!

--Krischik 14:51, 30 Nov 2004 (UTC)