Talk:Ada (programming language)
| This is the talk page for discussing improvements to the Ada (programming language) article. This is not a forum for general discussion of the subject of the article. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
| Archives: Index, 1, 2, 3 |
 | Computing C‑class High‑importance | |||||||||
| ||||||||||
Ada Home
- Ada Home - Old Web Site for Ada (not maintained)
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 describing a programming language a link to a different side should be enough. Ariane 5 Failure
I agree with that. it seems to me that this topic has nothing to do in an article describing a programming language all the more since it is rather a human error than a weakness of the language.
--Tarroux 07:28, 24 February 2007 (UTC)
- It is relevant because Ada advocates claim that Ada doesn't allow these types of mistakes. That is, until someone brings up this incident or something like it, then Ada advocates say something else. Val42 23:21, 28 February 2007 (UTC)
- No, we Ada-Advocates claim that Ada can protect against these type of error - but you also can switch the protection off if need be. The ability to switch the protection off is an important feature of Ada - otherwise Ada would not be usable for System programming. Krischik T 07:46, 12 March 2007 (UTC)
The statement that this incident caused the Ada runtime error checking to be questioned (I have been working with Ada for 20 years and have never heard this). This statement has no citation; the full report on the incident does not cite the Ada language as a contributing cause of the accident only the specification and design of the software. I believe this statement should be supported by a citation or removed. Richard A Brown 18:05, 9 March 2007 (UTC)
- Yes, we do need a citation. This statement should be marked as needing a citation (if it hasn't already). Then after at least two weeks, if there is no citation provided, it should be removed. Val42 06:01, 10 March 2007 (UTC)
- We originally added this chapter because the Ariane 5 failure is often used by Anti-Ada-Advocates to spread FUD. Isn't it great that the Anti-Ada-Advocates can spread there false claims unhindered why we are asked to provide more and more citation. We have the full wikisource:Ariane 501 Inquiry Board report on Wikisource, 3 References and 5 External Links on the main article - but no that is still not enough! Down with the truth, FUD rulez! --Krischik T 07:46, 12 March 2007 (UTC)
In any case, a human-error "let's just import the program directly" example isn't a criticism. "It's unweildy and unpopular" would be criticisms... and before anyone jumps down my throat, I don't know the first thing about Ada, so those were just vague examples. I'd love to see a criticism section like the one in C++ or COBOL#Criticism, but until then, I'm just going to axe it and request an expansion. --The Centipede 20:00, 15 August 2007 (UTC)
- I agree that this section needs to be rewritten. I have never understood the insistence on talking about Ariane 5 in this page. True, this story has been used to criticize Ada, but I don't find it useful to litter this page with all sorts of badmouthing about Ada.
- In fact (but this would probably belong to the flight 501 page) it would be more interesting to ask if there is a programming language design that would have helped in this instance. In C and C++ the effect of the conversion would have been "undefined" (meaning: anything goes). In Java it would have saturated. In C#, an exception would have been raised. Now because this particular piece of software was not actually in use, not raising an exception would have been preferable. But the important point is that there is no way that a programming language could guarantee some reasonable behavior after an unreasonable conversion.
- There have been valid criticisms levied against Ada, and it would be interesting to list them and give a balanced view of their merits. But this is not what this section is doing. -- PascalLeroy 14:04, 20 August 2007 (UTC)
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.
--- Sorry, but that's a rather pointless and not only invalid but also uninformed statement, in fact you may be surprised that software compilation regularly involves translating high level code into ASSEMBLY language, which -surprise- usually happens to be even less-(strongly) typed than any conceivable high level language, so the point really isn't the target language/representation that a high level language is translated to, but rather how (strictly) this is done and how it is enforced that the corresponding rules are enforced.
Thus, only because a compiler for a very strongly typed language (such as Ada) may -in fact, routinely- translate source code to a less-strongly or even virtually untyped target/intermediate representation (like C or directly assembly), this doesn't necessarily imply that the strongly-typed nature and goals of the original language is automatically affected and may thus be questioned: once compilation has taken place and succeeded, it doesn't matter for an Ada program whether its target language is C, Java, Pascal, Python or assembly, simply because until then numerous rules have been applied to the original code, ensuring to a very high degree that the underlying source code can in fact be properly transformed to (a subset of) the target representation. The real potential pitfall in such a scenario would in fact lie in 3rd party software that may translate the produced -valid- output to another target language possibly not applying similarly rigorous rules, however this issue is routinely addressed by settling for a well-defined and very limited subset of the target language which can be easily verified and validated using a corresponding test suite.
This approach is for example also taken by the SPARK language (a dialect/subset of Ada): Being basically a subset, SPARK programs are necessarily valid Ada, however they're being written with lots of meta information about expected and desired runtime behavior, this very meta information is provided in the form of comments in the source code, so it would not really affect an Ada compiler, a SPARK compiler however will happily process and honor such comments to parse, validate and augment the source code to come up with an accordingly enriched Ada program. So, this is again an example for a scenario where a comparatively strongly typed source language (SPARK) is translated to a less-strongly typed language (ADA) without necessarily compromising the safety margins provided by the source language and its specification.
- 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 !
- SofCheck licenses its "AdaMagic" front end to a number of Ada vendors. There is one version of this front end that generates optimized ISO/ANSI C (though it is not widely used at this point). There is another version that generates Java byte codes ("AppletMagic"(tm)). The most widely used version generates a conventional compiler intermediate representation, and has well over 50,000 users. The version that generates optimized C is useful because it allows the use of Ada on platforms that might not justify the expense of building a fully integrated Ada compiler. The C-generating front end has enabled the use of Ada 95 on Crays, old Vax/VMS machines, old versions of the AIX operating system, 16-bit microcontrollers, etc. We love that. ;-)
- And actually, the USDoD has no particular connection to Ada anymore. The most loyal users of Ada are companies that like the low error rates that typically accompany developing in Ada, as well as those that are obligated to certify the safety of the software (commercial aviation, passenger rail, etc.). 209.6.248.170 14:20, 29 January 2007 (UTC)
See http://www1.acm.org/sigs/sigada/education/pages/myths.html for some answers to similar questions.--Parallelized (talk) 23:02, 1 February 2008 (UTC)
And: http://www.mil-embedded.com/articles/authors/gicca/ --Parallelized (talk) 23:12, 1 February 2008 (UTC)
theory books
Ada is used in a few compiler theory books because of its comprehensiveness and elegance.
Related websites:
primary users
Should there be a section on primary users of a language like ada and how their requirements affected the language?
Ada is today still routinely being used for efforts where safety-critical software systems need to be developed, this is for example the case for aviation and space technology (think ATC, avionics, engine control etc) but also lots of other government software (think traffic surveillance, control and management), whenever lives or great financial resources are at stake, crucial software components are still being developed in Ada or even more rigorous subsets of it (i.e. SPARK). Likewise, for many such safety-critical software projects there are very high safety requirements to be met, which are often easier to satisfy by using Ada (critical software in railway control systems or even nuclear power plants, must have a well-defined and easily verifiable runtime behavior).
Also, Ada is also frequently the first choice when it comes to guaranteeing a high degree of maintainability for long-term software projects.
For additional in-depth resources, see the Ada wikibook and its discussion/talk page which features a "resource" section about Ada, its primary uses and benefits. —Preceding unsigned comment added by 82.83.66.83 (talk) 13:23, 21 January 2008 (UTC)
See this website for an overview of Ada users and application areas. Someone might want to incorporate some of this into the actual article. --Parallelized (talk) 22:42, 1 February 2008 (UTC)
Pascal
Ada has some tastes of Pascal still but not one of the bad ones. --Janet Davis
Well both Ada and Pascal are based syntactically on ALGOL 60, so that's not much of a surprise. Ada certainly took some ideas from Pascal, but fixed it's problems. —Preceding unsigned comment added by 68.222.42.172 (talk) 21:12, 18 January 2009 (UTC)
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
Development History: If possible a table summarizing the roughly 17-18 received, all but one Pascal-based designs, with names or references preceding the four finalist colors would be good. Any distinct features might be noted before their developers fade to dust. 143.232.210.150 (talk) 17:44, 14 May 2008 (UTC)
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
- The Ariane failure occurred in a piece of the code that has no function in flight (only useful on ground). It was a simple run-time overflow of an float to integer conversion. Since the exception trapping and handling in Ada is somewhat heavy and it was thought that this overflow could not occur, no exception handling was present in this part of the code. In Ada, unhandled exceptions generated propagation to calling levels, this overflow condition propagated all the way up to the main line. Exceptions at the top level main line are handled with a CPU halt, with the assumption that a major hardware failure has occurred and a switchover to backup is needed.
- The reason that Ada by some is claimed as a contributing factor for the accident is that such a failure occuring in low level was not contained there, but propagated all the way to the top level code causing a halt. Common system design practise in space systems required that malfunctions in subelements are not propagated to other parts of the system.
- The article was misleading on this, I tried to make it more factual. Uffe 05:01, 2 September 2006 (UTC)
- PS. The reference used is very bad third level hear-say analysis by a group trying to promote some software called 'Eiffel' and has no bearing on subject.
- Note that it is only an extract from the main article. --Krischik T 07:51, 12 March 2007 (UTC)
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)
JGNAT, MGNAT and A#
I've moved JGNAT back to the compilers subsection and added MGNAT (Ada .NET compiler). I've also removind the reference to A# to the related programming languages subsection (that was put there by myself). I'm not sure whether A# is only the name of the project, or there are any extension to the Ada language (other than 'limited with', a feature that will be part of Ada 2005). Are the languages accepted by JGNAT and MGNAT a subset of Ada? (Can someone confirm this?) In that case, maybe it would be necesary to add a section called Ada dialects.
NOTE: I do not consider SPARK as an Ada dialect because it greatly changes the language with data & information flow analysis (adding formal annotations), therefore becoming another language. But if A# makes any chages (I suppose those are minor changes), I will consider it a dialect.
-- suruena 23:38, 2004 Dec 6 (UTC)
More a superset
I would consider JGNAT and MGNAT more a superset. In order to support the virtual mashines additional featuers are added: Garbage Collector - a must, interface inheritance, limited with, Object.Operation.
Yes, some of which will be part of Ada 2005 - but not all with the same syntax. And on top ObjectAda did the Java extension differently. The hope is that with Ada 2005 all both will fall in line again.
As for A# - Tricky to say since MGNAT is the only A# implementation - so mayby there are just two words for the same thing.
SPARC and "Dialect" - I see the word itself broader then you - The are german dialects which I can't understand - but I can understand SPARC programms.
But if you are a native english speaker you may find a more appropiate word.
Anyway, I think the current wording is OK for far and I would leave it as it is.
--Krischik 08:43, 7 Dec 2004 (UTC)
Embedded systems
I removed the Embedded systems cat (a language alone isn't a system) and got a note regarding Ada's intended use within that context. While I wouldn't suggest re-adding the category, I would suggest that someone incorporate that fact in the article itself to better clarify that fact.--Hooperbloob 06:46, 14 Feb 2005 (UTC)
As a software engineer involved in the development of Ada, I would like to see included in here a comparison with C and C++. Ada is one of the few programming languages certified by the DoD because we produce much more reliable programs, more resistant to hacking than other high order languages, e.g., C++. However, where speed is concerned, you really want to use either Assembly Language or C, an intermediate language. Ada still requires a lot of memory and has a high overhead. There are some compilers that allow an optimized, bare-bones Ada but they need to be carefully checked. I suggest having two compilers and compiling the source code on both. You'll find different bugs each way.
- I just wanted to start writing such a chapter but the first sentence in chapter "Features" allready reads: "Ada was originally targeted at embedded and real-time systems, and is still commonly used for those purposes.". --Krischik 18:19, 14 Feb 2005 (UTC)
Article improvements
- "It addresses many of the same tasks as C or C++, but with one of the best type-safety systems available in a statically typed programming language."
This sounds rather dubious to me. No cites, no specifics, simply an assertion. What sort of a type system? Strong, weak, optional type declarations or mandatory, duck-typing; any sort of type inference? For that matter, are there higher-order functions or any functional characteristics at all?
- The type discipline is described inside the info box (Typing discipline: static, strong, safe, nominative). As for the describing the type system - we should probable say more. Over at wikibooks we have two [1] [2] rather large articles on Ada's type system. --Krischik T 12:21, 9 May 2006 (UTC)
Why is the Ariane 5 section a top level section? That should really be a subheader of a (currently non-existent) Criticism section (I think a criticism section is definitely missing- the first time I ever heard of Ada was when some folks were criticising it). It's also kinda weasel-wordy.
- Read again: We are defeding Ada as the Ariane 5 failure was a rooted in mis-management. Neither the programmers nor the programming language are to blame. No criticism on Ada at all is deserved here. It is also one of the most changes sections as feelings run high here. --Krischik T 12:21, 9 May 2006 (UTC)
While we are talking about the headers, why the deuce is there an "Ada Wikis" section? That should be a subheader of External links, as none of them are notable enough to have their own article- and that's just in addition to the peculiarity of linking to Wiktionary definitions at all, much less in an "Ada Wikis" top level header. The See also section needs cleanup as well: they are not supposed to be red links. Move'em over into Ext. links as well.
- Yes - quite a few links here. Cleaning up is indeed needed. I also noted external links in "see also". --Krischik T 12:21, 9 May 2006 (UTC)
--maru (talk) contribs 23:56, 8 May 2006 (UTC)
Quite frankly, this entire thing looks like it was written by an unabashed Ada promoter. If it was about a product, I'd think somebody quite simply cut n' pasted promotional material from the company's website. There's also several spots in the entry that all but say that it's 'impossible' to write bad code in the language. I really wish Ada's fans would get it through their heads what they didn't back in the late 80's when you'd find one in damn near any programming shop (at least before C++ took off and Ada experienced a dramatic decline in mind share), which is it's possible to write bad code in ANY language, even stuff that's incredibly contract based like Eiffel. ALL programming languages represent trade-offs and compromises, and that includes Ada. This entry makes it sound like it's a bulletproof language that's will catch almost any error a coder might make ahead of time, which simply isn't true. It's not 1988 anymore, Ada fans, and some concessions to reality and the decline of the use of the language in the real world won't kill you. --Dh100 20:11, 29 June 2006 (UTC)
- True, you can not catch all errors in existence - but you can catch more then the competition - and it is only fair to mention that. I will reverse your argument: When will it be understood to the general programming community that it is possible for a compiler to flag
Date.Day := 33as an error. --Krischik T 12:53, 9 February 2007 (UTC)
The History and the Standardization sections have no mention of Ada 2005.--76.83.24.57 (talk) 06:20, 5 July 2008 (UTC)
Ada Mandate
Why has the cancellation of the Ada Mandate been deleted from the article page? Val42 04:34, 27 May 2006 (UTC)
- I suspect strongly it's because the Ada fans who wrote and watch over this page didn't care for it. --Dh100 20:02, 29 June 2006 (UTC)
Requested move
Ada programming language → Ada (programming language) – Conformance with WP naming conventions atanamir Moved. See: Wikipedia talk:WikiProject Programming languages/Renaming poll
Influences
- Extract from: http://archive.adaic.com/pol-hist/history/holwg-93/2.htm (source: portal.acm.org/ft_gateway.cfm?id=1057816&type=pdf)
- Without exception, the following languages were found by the evaluators to be inappropriate to serve as base languages for a development of the common language: FORTRAN, COBOL, TACPOL, CMS-2, JOVIAL J-73, JOVIAL J-3B, SIMULA 67, ALGOL 60, and CORAL 66.
- Proposals should be solicited from appropriate language designers for modification efforts using any of the languages, Pascal, PL/I, or ALGOL 68 as a base language from which to start. These efforts should be directed toward the production of a language that satisfied the DoD set of language requirements for embedded computer applications.
- Ada - DoD HOLWG, Col Wm Whitaker, 1993
I don't know what the complete list of functionality originally from ALGOL 68 is. Maybe concurrency, operators, overloading & strong typing. These were mostly missing from ALGOL 60. So I changed the "Influenced by:" to refer to ALGOL 68 directly.
NevilleDNZ 18:52, 23 November 2006 (UTC)
- I think you are misunderstanding the language here. The notion was to start with a "base language" and modify it to meet additional requirements (Steelman). All four finalists chose to start with Pascal, which was widely perceived as a simple, clean language. Of course, Pascal is also a very incomplete language, as it was intended for student programming (compare Wirth's Pascal with ISO Pascal), so a lot had to be changed/added. There was strong lobbying from the British MoD to work with Algol 68, but in the US it had a bad reputation (mostly undeserved, but that's another story). Beyond the base language, ideas were taken from all sorts of places, including Algol 68, CSP, etc. --Macrakis 18:33, 29 January 2007 (UTC)
Moved from article
- == Criticism ==
- === The Ariane 5 failure ===
- The maiden flight loss of Ariane 5 Flight 501, a European Space Agency Ariane 5 launcher, was due to an :error in a program written in Ada for checks of the launcher while on the ground. During the beginning of the flight a :run-time error occurred that was not covered by an exception handler and therefore propagated to the main guidance :program leading to main processor shut down and loss of guidance. Management of the Ariane 5 project had decided :that since the same program worked well for all the flights of the Ariane 4 it would be reused directly, without :being adapted, for the Ariane 5. For the Ariane 4 program, efficiency considerations had led to the disabling :of the software handler (in Ada code) for one error trap (a data conversion from a 64-bit floating point to 16-bit :signed integer value). However, the flight parameters of Ariane 5 were different and when one value failed a range :check that was impossible to fail on an Ariane 4 there was no code in place to handle the resulting exception. The :incident led to discussions on the use of Ada as a possible contributing factor, in particular concerning the design of :Ada's run-time error handling.
This is not a criticism. It is just an anecdote that does not explain anything related to Ada as a language. If someone can re-write the section so that it represents a critical view of Ada, then the section should be re-instated.
Wikipedia is not a place for folks with an axe to grind. Rather than complain about how "they" say "this" about Ada and then "something happens", provide a valid explanation of what the language spec provides and how it fails to meet the objectives. A legitimate explanation of the features and deficiencies will provide value to the article. However, the above section that I removed just downgrades the quality of the article without making any sense to an uninformed reader.Michael Daly 19:31, 20 August 2007 (UTC)
- Of course you are right. You see for us Ada advocates it is a very touchy part. Ada haters blame Ada for the failure - and they do so loudly. There argument is that Ada did not meet it's objective. Even you ask "how it fails to meet the objectives" - but that is the point: Ada never failed it's objective. The Ariane 5 management failed its objective and where probably looking for a Scapegoat. If runtime checks are explicitly switched off as part of a design decision then it's not the fault of the language. Actually the chapter should have been == Unfair Criticism == - but wikipedia does not normally carry such chapters. I sitting here and I am don't know what to do. Leave it deleted, was not a very good chapter really. Or is the FUD so widespread that it is of encyclopaedic value after all? Honestly I am torn here. --Krischik T 18:27, 31 March 2009 (UTC)
Pronunciation of Ada
What is the dominant pronunciation of "Ada?" I don't know if it's supposed to be /'æˑdə/ ("add uh") or /'eɪˑdə/ ("aid uh"). If you know, please add the IPA pronunciation to the article. GoodSirJava 14:14, 17 October 2007 (UTC)
- /'edə/, according to "A Pronouncing Dictionary of American English". But I don't see that the article needs it; it's just the English name Ada.--Prosfilaes 15:17, 17 October 2007 (UTC)
Further resources
See the Ada wikibook's discussion page for a collection of possibly interesting references: —Preceding unsigned comment added by 82.83.76.5 (talk) 10:27, 26 January 2008 (UTC)
Wirth programming language
Ada is not a Wirth programming language. Wirth did not create it. Ada is not a Wirth-like language; languages are vastly dissimilar to people. Ada may be a Wirthian language, but there's no agreement on that[1]. I fail to see this as a useful or clear category, and would like to see a better name, a clear definition of what a Wirthian programming language is, and to start out with ALGOL W, Pascal, and other self-evidently Wirthian programming languages before adding Ada.--Prosfilaes (talk) 04:08, 3 February 2008 (UTC)
- 10-Nov-2008: I tend to agree with not labeling Ada as a "Wirth-like" language, and so I had put the wording "extended from Pascal and other languages" rather than "based on Pascal" (as in October). Ada is a comb-structured language (4 teeth: "Declare-Begin-Exception-End"), where the semicolon ends a statement, and that is radically different from Pascal separators, where semicolons before an "END" have killed Pascal compilations (zillions of them). Because Ada is so much larger, broader than Pascal, I don't think any Wirth-like connections are very helpful for software readers, but perhaps instead, emphasize some major ways how Ada is NOT like Pascal. -Wikid77 (talk) 15:49, 10 November 2008 (UTC)
Real World Projects in Ada
Link to a page that shows real world projects that use Ada: http://www.seas.gwu.edu/~mfeldman/ada-project-summary.html 75.68.157.156 (talk) 10:21, 1 April 2008 (UTC)
Comments
The current text of the comments section is a bit strange. See commentary below:
- Ada was designed to use the English language standard for comments:
- What "English language standard for comments"? What does this refer to?
- the em-dash, as a double-dash ("--")
- Ada does not allow non-ASCII characters such as the em-dash (—) in programs; two hyphens in a row is the typewriter convention for writing dashes, that is all.
- to denote comment text.
- "--" does not 'denote' comment text, it begins it.
- Comments stop at end of line,
- This is all a very wordy way of saying that Ada has conventional line-end comments introduced by "--".
- so there is no danger of unclosed comments accidentally eating whole sections of source code.
- This is true of all line-end comments.
- Comments can be nested: prefixing each line (or column) with "--" will skip all that code, while being clearly denoted as a column of repeated "--" down the page.
- This is not the conventional sense of "nesting comments"; anyway, this convention words for any language using line-end comments.
- There is no limit to the nesting of comments, thereby allowing prior code, with commented-out sections, to be commented-out as even larger sections.
- This is a pretty vacuous statement, since it works with any line-end comments
- All characters are allowed in comments, such as for symbolic formulas (E[0]=m*c^2).
- Again, pretty vacuous.
- To the compiler, the double-dash is treated as end-of-line,
- No need to bring the compiler into the language definition.
- allowing continued parsing of the language as a context-free grammar.
- Yet another completely vacuous statement.
Lots of verbiage, no more content than saying "Ada has conventional end-of-line comments introduced by '--'". --macrakis (talk) 03:29, 5 November 2008 (UTC)
- 10-Nov-2008: I was attempting to add more detail for general readers, by adding phrases about the parallel to English--with the commentary notation. Also, the issues about unclosed-comments and nested-comments (comments within commented-out code) are major aspects of comment-syntax design. Noting the "parsing of the language as a context-free grammar" is a brief note emphasizing that the language design is very much concerned with the compiler. There are also several other aspects that I omitted for brevity; however, I think expanding (not reducing) the text would be a better avenue: adding a whole article section about Ada comment syntax and its impact, where readers would be expecting several sentences about the use of comments. I am thankful for the above analysis: without that suggestion to use fewer words, I might never have realized that many more words were needed. It can be so easy to view other people's concerns as "vacuous" when people forget about viewpoints of beginners or laymen. I have worked on clarifying many articles that people had labeled as "too technical" and needed more basic details for general readers. However, the best approach might be to write an intro article ("Introduction to Ada") as has been done with other detailed subjects. -Wikid77 (talk) 15:49, 10 November 2008 (UTC)
- I agree with Macrakis, that this part is too verbose. What should clearly stay is: That the double dash parallels english/natural languages (it’s in the 83 rationale, Section 2.1: As an end of line remark, the comment should appear as an explanation of the preceding text -- hence the use of a double hyphen (doing duty for a dash) is natural and appropriate, as illustrated by this sentence.), and that arbitrary characters are allowed inside comments (this is not invariably true in other languages and explicitly stated in the tinman requirements).
- But the benefits of line comments (no runaway comments, no problems with nesting, grep-friendly, easy to recognize) would IMHO better be elaborated in depth somewhere else. However, I ailed to find sources, except internet discussions, for the problems and merits of line and block comments, yet (WP:OR…)—any suggestions where too look for some? Rathgemz (talk) 22:30, 18 January 2011 (UTC)
confusing text
This article contains the following block of text, and I don't know precisely what it means. I suspect there is some missing punctuation. Anyone know what is trying to be said here?
The semicolon (";") is a statement terminator, so Ada avoids the very common problem where ";END" kills a Pascal compilation because ";" is only a Pascal separator, never allowed either to terminate "END;" in Pascal.
65.183.135.231 (talk) 20:28, 25 March 2009 (UTC)
is is needed at all
I wonder if this is at all needed. It is a detail which language lawyers are interested in - most normal developers never notice the difference between a statement separator and statement terminator as the difference only show in the quality of error message. More important is the null statement which is null; and not ;. Also ;; is illegal in Ada. --Krischik T 06:48, 26 March 2009 (UTC)
reads as an ad
This article reads as an ad - it doesn't even touch any criticism of Ada and fails to mention why this language is so rarely used, outside of US Military --195.113.21.159 (talk) 13:37, 6 April 2009 (UTC)
maybe because there noting wrong worth mentioning
I use Ada in daily and there is nothing I like to criticise. At least nothing substantial worth mention. Note that when I was using C++ there was a lot I liked to criticise about C++.
I could try to dispels some of the FUD around Ada like:
- to expensive
- there is a free Ada compiler as part of the GNU_Compiler_Collection.
- to complex
- the ISO standard for Ada 2005 is a whooping 3.8% larger then the ISO standard for C++ 2003. And with current amount CPU and Memory available it does not matter any more.
- no programmers
- The only which has some merits. But it's not the languages fault that companies do not want to train there workforce.
- only used by US Military
- Well, look here and here. Railways, Bank, Aviation, Non-US Military. You have fallen for a Hoax.
But then criticism sections have been discouraged on Wikipedia as such chapters only turn into troll magnets. We leave it as it is. Of course, if you find any substantially wrong with Ada which is not a Hoax or FUD then let me know.
--Krischik T 11:39, 7 April 2009 (UTC)
- So, at least, include some part, explaining or mentioning, why is Ada NOT widely used today. (It is not.) Are there historical reasons - and FUD? Probably ... but it should be, at least, mentioned. I won't do it, I don't have the needed knowledge. And I never said there is something substantially wrong with Ada. --Have a nice day. Running 19:01, 7 April 2009 (UTC)
- I love to. But you know, the main reason that most new Projects in our company are done in Java is the "replaceable-ability" of Java-programmers. Yes Hire and Fire as main reason for choosing a programming language. And this is Switzerland where people are nice to each other. But ranting about the management won't be very helpful explanation.
- Well maybe I can still fit something into the history section why Ada had slow to start and was never quite able to acquire the critical mass to become a "mass-market" programming language. --Krischik T 07:24, 8 April 2009 (UTC)
- [2] gives lines of code in Debian 3.1. Ada is the 11th most common language. Given the number of languages around since Ada was created and in use when Ada was created, I don't see the question as why it's NOT widely used today; the question is why is it so widely used when so many other languages have bit the dust? Sadly enough, the answers are just as arbitrary one way as the other in many ways; Ada is not used because C (and C++ and then Java) and Unix won for various reasons, ranging from the arbitrary (AT&T's legal woes) to the historical (once C and Unix got a foot in the door, C++ was easy to switch to, then Java), to the value-based. On the other hand, why is Ada thriving and Modula-3 dead? Because the DoD thrived and pushed their language and DEC died.
- In summary, the mere claim that Ada is not widely used today is biased by a demand that to be widely used, you have to be one of a dozen top-dogs. To ask why it's not one of those languages is the wrong question; the real question should be "why is it where it is?", which at some point drags in the life and death of at least a dozen unrelated languages and operating systems.--Prosfilaes (talk) 15:28, 8 April 2009 (UTC)
- "Ada is the 11th most common language." - wow, count me surprised. --Have a nice day. Running 12:32, 14 April 2009 (UTC)
Lacks a Lot
Page on Ada lacks the history of the APSE, The attempt to also standardize hardware, Larry Druffle, and it would be nice to have the cut before the colored proposals (the next to last dozen and a half). 198.123.48.76 (talk) 21:49, 12 May 2009 (UTC)
Language constructs
I seem a lack for "Language constructs" or "Syntax and semantics" for this article, something that is found on other articles like Pascal or Eiffel. —Preceding unsigned comment added by ARSHA (talk • contribs) 22:22, 16 June 2009 (UTC)
- You find this info in the award wining wikibooks:Ada_Programming. The question here is: how much syntax and semantic is encyclopaedic and when do we cross line into advertising or micro-tutorials. And personally I think some articles already crossed that line --Krischik T 06:58, 17 June 2009 (UTC)
- I took the Pascal section on syntax shortened and converted it to Ada. --Krischik T 11:17, 19 June 2009 (UTC)
The United States Air Force is not a reliable source?
Should we just delete all references to the USAF from WP while we're whitewashing this article? And BTW the ADA runtime comes fairly close to being an OS in its own right. Hcobb (talk) 02:45, 21 October 2009 (UTC)
- First, we don't know anything about ADA. This is the article for Ada. We can't even tell if the article is speaking about the language, or something else.--Prosfilaes (talk) 03:09, 21 October 2009 (UTC)
Stuff removed from Boolean data type article
The following section was removed from the article Boolean data type:
begin removed text
Ada (defined in 1979, implemented in 1983) defines Boolean in the package Standard as an enumerated type with values False and True where False < True.
type Boolean is (False, True);
p : Boolean := True;
...
if p then
...
end if;
The relational operators (=, /=, <, <=, >, >=) apply to all enumerated types, including Boolean. Boolean operators and, or, xor, and not are defined on Boolean and any declared subtype. The Boolean operators also apply to arrays of Boolean values.
end removed text
Is there a place for this text in the Ada-related articles? Perhaps in the Wikibook? Thanks, and all the best, --Jorge Stolfi (talk) 23:26, 30 December 2009 (UTC)
Unreliable source cited in Article
The source http://www.sldinfo.com/?p=325 is cited in the introduction as the source of the Former Secretary of the USAF blaming Ada for problems with many major military projects. The article claims that "the Defense Department specified in detail its own operating system, called ADA" and that it experienced problems "retain[ing] talent for ADA when careers were being made in DOS, Apple and LINUX." But Ada is not an OS; it is a programming language. Should such an uninformed source be considered reliable? ChrisPB (talk) 23:12, 13 February 2010 (UTC)
- It's written as an opinion piece, not to be confused with a factual presentation. The thing to do would be to see what the wider context is, and also whether there are corrobating sources. Tedickey (talk) 23:37, 13 February 2010 (UTC)
- Sure. Let's get an opinion on Ada, by somebody who's managed a department with more projects with more total Ada programmers at work at them, than Michael Wynne. Go right ahead. Hcobb (talk) 02:06, 19 February 2010 (UTC)
- That was a facetious comment, which doesn't address the point Tedickey (talk) 02:10, 19 February 2010 (UTC)
- It's the opinion of a well informed public official, based on his exposure to classified information. But I will see if CRS, GAO or CBO have tried to total up the cost of this boondoggle. Hcobb (talk) 02:40, 19 February 2010 (UTC)
- "Well informed"? Would you be saying that if he was complaining about the use of the military use of the M1 Abrams airplane when people were getting trained on 747s?--Prosfilaes (talk) 17:01, 19 February 2010 (UTC)
- Clarification: "the Defense Department specified in detail its own operating system, called ADA" Anyone else see the glaring problem here? Ada is NOT an OS, so either the source isn't talking about Ada [the language], or he's really confused himself somewhere down the line. Do we even know for sure he was referring to the Ada language? --151.190.254.108 (talk) 14:31, 22 June 2010 (UTC)
- Well, Hcobb asserts that the source is a "well informed public official", which makes him a WP:RS (only in the Wikipedia sense, of course), without making any points on whether Wynne actually is a suitable source. There probably are more well-informed sources Tedickey (talk) 20:38, 22 June 2010 (UTC)
Java influences
In which aspects was Java influenced by Ada, and Ada 2005 influenced by Java? --Abdull (talk) 23:27, 13 September 2010 (UTC)
- The big one was that Ada 2005 has Java-like interfaces.--Prosfilaes (talk) 07:29, 14 September 2010 (UTC)
- That can't be true. The interfaces are from Ada 83, and at that time Java wasn't even conceived in a mystical hallucination. Of course Java borrowed it from Ada 83! Java copies some features from everywhere, but invents nothing by itself (the advantage of Java is JRE, which is outside Java). Rursus dixit. (mbork3!) 07:10, 30 September 2010 (UTC)
- I updated article accordingly. It's a really bad thing that such editor-inferred speculations are added as facts in the articles. All such alleged influences should be painstakingly cited by the original source(s), i.e. the inventors themselves or the design rationales that they produced. Rursus dixit. (mbork3!) 08:12, 30 September 2010 (UTC)
- That can't be true, huh? "A major improvement is that Java-like interfaces are introduced thereby permitting simple multiple inheritance" from the Ada 2005 rational. I think it behooves you, before you get emotional about something, to check it first.--Prosfilaes (talk) 08:30, 30 September 2010 (UTC)
- 1. OK, thanks for the link, I was wrong.
- 2. "behooves you"? Are you taking it personal?
- Best wishes. Rursus dixit. (mbork3!) 11:13, 5 October 2010 (UTC)
- FYI: The Java like interfaces are in Ada 2005. I was unaware of that version. Rursus dixit. (mbork3!) 11:17, 5 October 2010 (UTC)
- Then perhaps when someone asked about how "Ada 2005 [was] influenced by Java", you shouldn't aggressively disagree and complain about how it's such a bad thing that "such editor-inferred speculations are added as facts", if you don't know about Ada 2005.--Prosfilaes (talk) 20:06, 5 October 2010 (UTC)
Object orientation
I don't have time just now to add the info, but object orientation is performed by writing packages that provide access types referring to private records. These private records are accessed through functions (c.f. methods in C++ and other class-oriented OOPLs) allowed access to those records. The syntax is pretty much deviant from C++, but there are no syntax doublettes like C++:es struct/namespace/class semantic overlap nor Java:s class/interface semantic overlap. (In that meaning Ada95 is cleaner, which is my POV, and not citeable.) Rursus dixit. (mbork3!) 07:21, 30 September 2010 (UTC)
- The syntax in Ada 2005 is a lot more similar to that of C++.--Prosfilaes (talk) 08:31, 30 September 2010 (UTC)
Smalltalk
The info box states that Ada95 has been influenced by Smalltalk. Is there a reference for that? I was just (unsuccessfully) trying to find out what features have been influenced, so some citation to follow up would be nice.