Search

This is a slightly polished version of an extended version of a talk given by the author at a Symposium in Oxford to celebrate the 200th birthday of Ada Lovelace in December 2015. It starts with a few words about Byron and his Bear at Cambridge. This is followed by some remarks about Babbage who also went to Cambridge and was involved in an important event involving Brunel and Safety on the Railways. The main topic is a look at the events that led to the new programming language devised to satisfy the needs of the US Department of Defense and which was named Ada in recognition of the fact that Ada Lovelace was the world's first programmer. The polishing is in celebration of 40 years of the Ada User Journal. [ABSTRACT FROM AUTHOR]

This paper describes the rationale for the changes made to Ada 2012 as a consequence of a review carried out in 2015. [ABSTRACT FROM AUTHOR]

This is an extended version of a talk given by the author at a Symposium in Oxford to celebrate the 200th birthday of Ada Lovelace last December. It starts with a few words about Byron and his Bear at Cambridge. This is followed by some remarks about Babbage who also went to Cambridge and was involved in an important event involving Brunel and Safety on the railways. The main topic is a look at the events that led to the new programming language devised to satisfy the needs of the US Department of Defense and which was named Ada in recognition of the fact that Ada Lovelace was the first programmer. [ABSTRACT FROM AUTHOR]

This is the last of a number of papers describing the rationale for Ada 2012. In due course it is anticipated that the papers will be combined (after appropriate reformatting and editing) into a single volume for formal publication. This last paper summarizes a small number of general issues of importance to the user such as compatibility between Ada 2012 and Ada 2005. It also briefly revisits a number of problems that were considered for Ada 2005 but rejected for various reasons; the important ones have been solved in Ada 2012. Finally, it discusses a small number of corrections that have been found necessary since the standard was approved. [ABSTRACT FROM AUTHOR]

Ian (piano), Paul (piano) and Celia (violin) were all excellent amateur musicians, so one must not see Ian as having nothing to do when he was not doing a little light consultancy to keep his hand in. Ian Wand is survived by his wife, Helen, children Paul and Celia, and their families. 188 Volume 41, Number 3, Septembre 2020 Ada User Journal In memoriam: Ian Christopher Wand Ian C Wand, Computer Scientist, was born on 10 December 1941 and died on 17 July 2020. [Extracted from the article]

This paper describes improvements to the predefined container library in Ada 2012. [ABSTRACT FROM AUTHOR]

This paper describes various relatively minor improvements to the predefined library in Ada 2012. The major changes concerning the container library will be described in a later paper. [ABSTRACT FROM AUTHOR]

This paper describes various improvements in a number of general areas in Ada 2012. There are some minor but perhaps surprising changes concerning matters such as the placement of pragmas and labels. There are important new features regarding indexing and accessing largely introduced to simplify iterating over containers. There are also a number of additional Restrictions identifiers many related to the introduction of aspect specifications. The functionality of access types and storage management is made more flexible by the introduction of subpools. Finally, a number of minor additions and corrections are made to a range of topics such as generics. [ABSTRACT FROM AUTHOR]

This paper describes various improvements in the tasking and real-time areas for Ada 2012. The most important is perhaps the recognition of the need to provide control over task allocation on multiprocessor architectures. There are also various improvements to the scheduling mechanisms and control of budgets with regard to interrupts. An interesting addition to the core language is the ability to specify restrictions on how a procedure of a synchronized interface is to be implemented. [ABSTRACT FROM AUTHOR]