Draft 2, 24 November 2008, Joyce Tokar
In accordance with Resolution 54-5, the next meeting of ISO/IEC JTC 1/SC
22/WG 9 will be held in conjunction with the SIGAda conference, beginning at
Conference and venue information can be found at the conference web site.
The announcement and preliminary agenda for this meeting were circulated as N492.
The meeting began at
Clyde Roby has volunteered to serve as meeting Secretary.
The meeting agenda is shown here.
The draft minutes of Meeting #54 are recorded in document N490.
|
|
Dirk Craeynest (HOD) |
|
|
|
Brad Moore (HOD), Stephen Michell, Luke Wong |
|
|
|
Jean-Pierre Rosen (HOD) |
|
|
|
Peter Hermann (HOD) - absent |
|
|
|
Tullio Vardanega (HOD) – unable to attend |
|
|
|
Kiyoshi Ishihata (HOD) |
|
|
|
Urs Mauer (HOD) – unable to attend |
|
|
|
John Barnes (HOD) |
|
|
USA |
Robert Dewar (HOD) |
|
Ada-Europe |
Erhard Ploedereder |
|
|
SIGAda |
John McCormick |
|
|
WG23 - aka OWG: Vulnerabilities |
Erhard Ploedereder |
|
Convener |
Joyce Tokar |
|
Webmaster |
|
|
ARG Rapporteur |
Ed Schonberg |
|
HRG Rapporteur |
Alan Burns |
|
PRG Rapporteur |
Stephen Michell |
|
Project Editors |
ISO/IEC 8652: Erhard Ploedereder, Randy Brukardt , and Pascal Leroy (unable to attend) ISO/IEC 13813 and 13814: Don Sando, Jon Squire and Ken Dritz (all unable to attend) ISO/IEC 14519: Ted Baker (unable to attend) ISO/IEC 15291: ISO/IEC TR 15942: Brian Wichman (unable to attend) ISO/IEC 18009: Erhard Ploedereder ISO/IEC TR 24718: Alan Burns |
|
Guests: |
|
Received from D. Craeynest,
National Body Report for
The Belgian Ada community ideally would like to see one integrated
ISO document corresponding to the current unofficial consolidated Ada 2005
Reference Manual, which also integrates the approved Ada 2005 AIs and possibly some new changes that might be
required. No preference was expressed for the specific ISO procedure to
follow to reach that goal.
There's no news to report about the changes (announced at the previous meeting)
in the way the Belgian National Body will work and how it will designate it's
representatives in the various ISO working groups. For now, and pending new information, the
Belgian delegation in WG9 continues to work as before.
Received from B. Moore,
Received from J.P. Rosen,
The Ada Group of AFNOR met on 2008-10-16, in preparation for the WG9
Portland meeting.
The group reviewed the proposed AIs. We noted that
the provided link (AI05-SUMMARY.HTML) was not up-to-date, since two AIs (104 and 105) were missing; fortunately, they were
easily retrieved from the AI data base.
Regarding the future of Extended containers (Resolution 50-5):
Regarding future direction of the
On the technical side:
On the editorial side:
The natural way of incorporating AIs is by producing a TC, however this would not meet the
goal of having a self-contained document.
It is clear that there is no desire (nor funding) for making big changes to the
language, although the outcome of WG23 (vulnerability) should be closely
watched. A possibility is to go formally for a revision, but without any change
beyond:
• producing the integrated document resulting from TC1+Amdt1
• incorporating AIs
• possibly adding some predefined packages (like extended containers, UTF8/16 coding functions, etc)
• possibly adding some pragmas if the outcome of the work of WG23 determines some needs that could be fulfilled that way.
Such a revision (minor in effect) would also send a positive message to the world that the language is alive and well.
Unofficial
Received from T. Vardanega,
1) Work performed
Struggled to keep up with the ARG work, with
particular attention to the (few) AI that have a bearing on real-time issues.
Willing and interested in investing effort in resuming HRG work for the
production of a language-specific annex to the OWGV report.
2) Issues
of interest
2.1) Unfinished business
No position at this time.
Will follow up the ARG discussion until the time of the WG9 meeting and may provide an opinion by then.
2.2) New business
Being the host for the SC22 meeting this year, I have taken the opportunity of talking to Sally Seitz to better understand the ISO-side implications of the various options.
I have therefore come to form the following opinion:
Italy consider that to fully update the Ada Standard, similar to what was done for Ada 95, is too much effort at this stage of development and user awareness of the current language standard.
It is also clear that a corrigendum is too complex
for common users: the Ada Issues that have been written up and resolved for Ada
2005 need to be incorporated into the Standard.
According to the SC22 Secretariat, in fact, it is possible to produce a new
EDITION that incorporates the corrigendum without the expense and overhead of a
new REVISION. A revision would in fact open the whole standard up for review
and be for an expansion or significant change.
I wish all attendees a productive meeting and an excellent time.
Received from J. Barnes,
A recent meeting of the BSI Ada
panel discussed at length the issue of the form of the next version of
This is the
view of IST5/-/9, the
1. We strongly believe that it should not be just a Corrigendum.
There are a number of issues that undoubtedly will have to be addressed soon and these cannot be treated as just errors in the existing standard. Moreover, working on just errors is boring and there is a real risk that the volunteers/experts will just fade away.
2. This leaves the choice between an Amendment and a Revision.
Strategically we feel that it is time to get away from the current medley of documents. Ada 2005 is defined as Ada 95 plus a Corrigendum plus an Amendment. To do another Amendment means that the resulting language would be defined by the interaction between four documents. Already the situation would be intolerable were it not for the energies of our editor and the good services of Springer-Verlag. It is bizarre that in practical terms the language is defined by a proprietary book and not by an official document.
Moreover, the UK MoD has a preference for ISO standards (over commercial or national standards) provided that they have been transposed by the BSI. It is not clear that the BSI likes transposing lots of bits and pieces; there have been occasions when the introduction of a Corrigendum has resulted in the BSI just withdrawing the standard. And in any event it would just be transposing the medley and not the coherent whole and can result in merely sticking a cover on the group of incoherent documents.
A key practical advantage of doing a Revision is that we just have to produce the one document for ISO and not all the curious "change this to that" stuff.
3. So what might be the problems with doing a Revision?
Have the ISO rules regarding layout etc changed so that everything has to be redone?
Would the paragraph numbers have to be consolidated? Maybe not since they do not appear on the ISO document anyway. And there seems no problem with keeping the current system (with modification history intact). Compiler error messages that use such numbers would not need modifying.
Would we lose the copyright? Presumably not if we were careful.
Would we be tempted to change too much? Clearly we must resist this. Enough troubles (anonymous access types and coextensions come to mind) were added in 2005. A key goal must be to keep the new stuff to the necessary. Doing just an Amendment gave plenty of opportunity for change. We would sincerely hope that the changes from 2005 to 2013 would be smaller than from 95 to 2005.
Would a Revision be too much effort - that is cost too much? Not if we keep the delta small.
And would there be a risk that customers would be nervous and think that since it is a Revision it must be a big change like 83 to 95. The message has to be that it is a Consolidation.
4. Conclusion
We recommend a Revision rather than an Amendment. Definitely not another Corrigendum.
Received from R. Brukardt,
Summary:
Reasons:
(1) A Corrigendum does not offer much to users (just bug fixes).
(2) A Revision is more risky than an Amendment, as it has the potential to add confusion due to renumbering of clauses, rewording of text, use of new/changed terminology and more. One participant called it an "apocalyptic earthquake".
(3) Users
and the world have expressed interest in additions to
(4) We expect the changes to be more contained than the last Amendment (not affecting as much of the standard).
(5) An Amendment or Revision will provide more energy (and potentially participants) in the process. New ideas are more interesting than bug fixes.
(6) An
Amendment or Revision would make
Risks:
(1) Some
organization needs to step up to create a consolidated standard (as Ada Europe
did in the last cycle). Otherwise, in the absence of a full revision,
(2) Some funding will be required. If that cannot be found, progress will be much slower or non-existent. (But this is true of all of the options.) Development of the last Amendment was more than a half-time job for 3 years; that level of commitment is unlikely from a pure volunteer.
Ada-Europe is a Category C Liaison to WG9 (See N414)
Received from
The
Beyond the publishing of John Barnes' Ada 2005 Rationale with Springer Verlag in time for the
Agenda
SIGAda is a Category C Liaison to WG9 (See N414)
From Meeting #53, in
At SIGAda’s Extended Executive Committee (EEC) meeting, there was discussion
about the status of the Ada Style Guide, i.e., who owns the copyright, etc.
SIGAda is currently investigating copyright issues from the Software
Productivity Consortium (the SPC owns the copyright although, from their
website, they do not have any
A question brought up here at WG9 concerned whether or not the AJPO (now non-existent) still owned a/the copyright to the Guide; if so, can WG9 (or anybody else) modify it? Opinions brought out during discussions here at WG9 indicate that the copyright evidently is still with SPC.
It was also brought up at the EEC meeting that a SIGAda member wanted to print and distribute the Ada Reference Manual (ARM) to all SIGAda members. Is this in conflict with Springer publishing “rights”? If this is done, is it in competition with Ada-Europe’s printing of the ARM? Evidently ACM’s lawyers are basically worried about printing and distributing the ARM – and denied permission to do it.
The ARG is very interested in learning more about the resolution of the
copyright issues as this may be helpful with the updates of other
Presently, it looks like the copyright is to AJPO; essentially this means the US Federal Government.
There is interest from the user community for this document. SIGAda will keep WG9 informed on the progress in the development of this guide.
The OWG: Vulnerabilities was an ad hoc Working Group of ISO/IEC/JTC1/SC22 (see N469). At the plenary session of ISO/IEC/JTC1/SC22 in September 2008, the Other Working Group was instantiated as Working Group 23 of ISO/IEC/JTC1/SC22
Received from
The OWG had a meeting in
In the near future, the WGs of SC22 will be contacted and asked to comment on
the PDTR and to write their language-specific annex. A template for the
structure of the annex will be provided.
The liaised WGs will have some opportunity to shape the structure of the
annexes and the text of the PDTR (which, in many cases, is written in a very
C-oriented terminology). The liaisons into the
Will the terminology of “vulnerability” be changed to
“weakness?”
The OWG has been renamed WG23.
The next meetings are in
The long break is caused by the committee draft process. In December 2008 there
will be an editorial telecom.
Early versions of the Technical Report (TR) documents are to
expose this work to the more general community.
Comments are very important.
WG29 is looking for WG9 to do a good review. The TR is expected to be
released by SC22 for review in November, which means that the commenting period
will be ending in the 2009 January or February. Since this works was initially
tasked to the HRG, we will discuss this further during the unfinished business section. The April WG23 meeting will be reacting to
comments submitted; possibly July too.
Entire process to publish the TR may take about 5 calendar quarters.
Some people are trying to include non-language
vulnerabilities, such as program environment vulnerabilities. Presently, this
goes beyond the scope of WG9’s interest.
In terms of what WG9 is used to with respect to programming
rigor, the OWG document is “lousy”. In terms of what the C language people are
used to, the OWG document is much better.
“Vulnerability” changed to “Weakness”?
Text of PDTR needs to be abstracted above languages, that
is, language-independent. Current examples in main part of document will
probably be moved into Annex, but undecided until first Annexes come in. WG23 is strongly encouraging WG9 to provide
an example of a good annex by providing one for
At Meeting #50 (N470), we learned that SC22 has created a project to provide a cross-language comparison of the vulnerabilities that exist in various programming languages and the manner in which these vulnerabilities may be avoided or mitigated. At the JTC1 SC 22 Plenary the OWG was converted into a Working Group under SC 22 – WG 23.
The most important work for this meeting is to come to closure on the path
forward for the
In addition, we will continue the various items of work underway, including:
ASIS – what is the progress on the development of this update and what is the schedule will be for completion,
POSIX/Ada binding – leadership and direction, and
market prospects. Something will probably not be
ready for submission in 6 months, but much later.
This is the "To Do" list for WG9. Some are informal action items assigned to various participants. Some are formal resolutions, which are not yet implemented. Some items are simply in suspense awaiting action by other groups.
[Editor, TR 24718] Monitor implementation by ITTF of free availability for ISO/IEC TR 24718.
For status, see: [Project Editor Maintenance Report, 24718]
ISO/IEC JTC1/SC22/WG9 recommends to SC22 that the following Standard be
confirmed when it reaches the end of its five-year review period: ISO/IEC
8652:1995, Information Technology--Programming Languages--
For status: CLOSED
Investigate the possibility that ANSI might be willing to sell the revised ASIS standard ISO/IEC 15291:200x inexpensively, i.e. at a price similar to that of programming language standards -- $18.
Status: Open. It has been
surprisingly difficult to obtain the appropriate contact information. Bill
Thomas will look into this further and get back to us at the next meeting
(#56).
WG9 requests that the ARG consider solutions to the problem described in comment 12 of N459 [containers], as well as other possible extensions to the standard library, and develop a New Work Item Proposal for a Type 2 Technical Report that will provide a "trial use" specification to users and implementers, and that will be suitable for future standardization.
For status: Open. Work is
proceeding at pace. There is a draft underway and is being tracked by the
Noting the current systematic review of ISO/IEC 14519 and the absence of any
working group responsible for maintenance of the standard, SC22/WG9 recommends
to SC22 that the standard should be confirmed in the current review and states
its willingness to accept the editorial responsibility for the standard. It
offers the services of Steve Michell (
For status: See [Project Editor Maintenance Report,
14519]
ISO/IEC JTC1/SC22/WG9 recommends to SC22 that the following Standard be withdrawn when it reaches the end of its five-year review period:
For status: Open. Still has not reached the proper level to be withdrawn – still pending. See [Project Editor Maintenance Report, 13813]
Resolution 53-5
scheduled meeting #54 in conjunction with the 2008 Ada-Europe conference,
Friday morning,
Resolution 54-5
scheduled meeting #55 in conjunction with the 2008 SIGAda conference on the
afternoon of Thursday afternoon,
The resolution offered below confirms the previous resolution and states the
intention of WG9 to colocate meeting #56 with the
2009 Ada-Europe conference.
ISO/IEC 8652:1995 Information Technology--Programming Languages--Ada, 22.10.01, Randy Brukardt and Erhard Ploedereder, Project Editors, supported by the Ada Rapporteur Group.
ISO/IEC 8652:1995/COR.1:2001, Technical Corrigendum to Information Technology--Programming Languages--Ada, 22.10.01, Randy Brukardt and Erhard Ploedereder, Project Editors, supported by the Ada Rapporteur Group.
ISO/IEC 8652:1995/AMD.1:2007, Amendment to Information Technology--Programming Languages—Ada, Randy Brukardt and Erhard Ploedereder, Project Editors, supported by the Ada Rapporteur Group.
Maintenance action recommendation is due in <TBD> for systematic review in <TBD>.
Project Status
The request for subdivision [N388] of Project 22.10.01,
to create AMD.1 was endorsed by WG9 Resolution 40-7 [N389],
and approved by SC22 N3310 on 2001-09-12. The project editors are Randy Brukardt and Pascal Leroy, supported by the Ada Rapporteur
Group. Preparation of the Working Draft was delegated to the
WG9 requests the project editor of the 8652 amendment to remain prepared to respond to any request from ITTF for a manuscript of a third edition to 8652.
ISO/IEC JTC1/SC22/WG9 recommends to
SC22 that the following Standard be confirmed when it reaches the end of its
five-year review period: ISO/IEC 8652:1995, Information Technology--Programming
Languages--
Status: The ISO web site
indicates that systematic review is underway.[jlt1]
The ARG is continuing maintenance on the standard; see the ARG report for details.
No resolution.
ISO/IEC 13813:1998, Information Technology--Programming Languages--Generic Packages of Real and Complex Type Declarations and Basic Operations for Ada (including Vector and Matrix Types), 22.10.04, Don Sando and Ken Dritz, Project Editors
The standard addresses the
ISO/IEC 13814:1998, Information Technology--Programming Languages--Generic Package of Complex Elementary Functions for Ada, 22.10.05, Jon Squire and Ken Dritz, Project Editors
WG9 has voted to withdraw this standard by year-end 2004. (The action awaits
implementation by ITTF.) The standard addressed the
ISO/IEC JTC1/SC22/WG9 recommends to SC22 that the following Standard be
confirmed when it reaches the end of its five-year review period:
ISO/IEC JTC1/SC22/WG9 recommends to SC22 that the following Standard be
withdrawn when it reaches the end of its five-year review period:
ISO/IEC JTC1/SC22/WG9 recommends to SC22 that the following Standard be withdrawn when it reaches the end of its five-year review period:
Status: OPEN. The recommendations above were endorsed by SC22 Resolution
01-07 at their September 2001 plenary meeting. They have been forwarded to JTC1
for approval (during 2003) and implementation by ITTF (during 2004). However,
JTC1 voted to confirm ISO/IEC 13814 rather than withdraw it as requested by WG9
and SC22. The SC22 Secretariat conducted a letter ballot authorizing it to
request that JTC1 reconsider its action. Accordingly, the request was sent to
JTC1 and JTC1 responded by circulating a letter ballot (J1N7405) to withdraw
the standard. The ballot ended on
No report.
ISO/IEC 14519:2001 Ed. 2, Information technology -- POSIX Ada Language Interfaces -- Binding for System Application Program Interface (API), 22.21.04.02, Ted Baker, Project Editor
In 2005, this document was reassigned by SC22, from WG15 to WG9.
Noting the current systematic review of ISO/IEC 14519 and the absence of any
working group responsible for maintenance of the standard, SC22/WG9 recommends
to SC22 that the standard should be confirmed in the current review and states
its willingness to accept the editorial responsibility for the standard. It
offers the services of Steve Michell (
Status: SC22 reassigned the standard to WG9 with Ted Baker as project editor. Processing of the document's confirmation by systematic review has not been completed.
Email note from Ted Baker,
I regret to say that will not be able to attend. I have exchanged several e-mails with Stephen Michell on the subject of the POSIX Ada binding standard. I provided him with a pdf version of the POSIX Ada binding document, so that he and a group of Canadian colleagues could review it. I understand that they will be estimating the scope of work that would be required to bring the standard up to date with respect to Ada and the base POSIX/Unix C-language API. There have been a few other exchanges, with a representative of Adacore Technologies and a user. The scope of the project can be scaled to fit the available human resources, by limiting the changes to only features that are not already provided by the existing POSIX Ada binding and the Ada language *and* have been requested by members of the Ada community. To this end, it might be reasonable to ask WG9 representatives to provide some e-mail lists of individuals and organizations that we could poll, to determine a list of features for which there is a demand.
No report.
ISO/IEC 15291:1999, Information Technology--Programming Languages--Ada Semantic Interface Specification (ASIS), 22.15291, Clyde Roby and Greg Gicca, Project Editors, supported by the ASIS Rapporteur Group.
This document was "confirmed" by JTC1 in its 2004 systematic review.
Report from Meeting #54
The scope of the ARG's ASIS activity is "to add or modify interfaces of the current ASIS specification in order to permit representation of the new language features that have been added to ISO/IEC 8652 since 1995. Care should be given to backward compatibility of existing ASIS applications."
A collection of ASIS items have been developed to meet this objective. To date, 24 SIs have been approved by the ARG and incorporated into the latest draft of the document. Eight SIs are still in work: SI99-0007, SI99-0019, SI99-0021, SI99-0024, SI99-0030, SI99-0035, SI99-0036, & SI99-0037.
Of these, most require only minor work. The largest and most difficult is SI99-0024, the purpose of which is to provide a semantic model in addition to existing syntactic model. The model has been developed, but needs additional review, as well as agreement on an approach for its documentation.
Additional action that is likely needed includes an update to the "ASIS technical concepts" section, both to be consistent with the current standard (e.g., remove references to obsolescent features), as well as to illustrate use of the new features (e.g., the semantic model).
Completion of SI-024, (and the related changes to other parts of the document) is likely to require several additional meetings. Having a complete draft available by the Ada-Europe 2009 meeting seems achievable, but prior to that may be challenging.
Received from B. Thomas,
The scope of the ARG’s ASIS activity is “to add or modify interfaces of the current ASIS specification in order to permit representation of the new language features that have been added to ISO/IEC 8652 since 1995. Care should be given to backward compatibility of existing ASIS applications.” A collection of ASIS items have been developed to meet this objective. To date, 26 SIs have been approved by the ARG and incorporated into the latest draft of the document.
Ten SIs are in work, six that were discussed at
previous meetings (SI99-007, SI99-019, SI99-021, SI99-024, SI99-033, and
SI99-037), and four that are new (SI-038, SI-039, SI-040, and SI-041). The
largest and most difficult is SI99-0024, the purpose of which is to provide a
semantic model in addition to existing syntactic model. The model has been
developed, but the wording describing the model needs review.
Additional action that is likely needed includes an update to the “ASIS
technical concepts” section, both to be consistent with the current standard
(e.g., remove references to obsolescent features), as well as to
illustrate use of the new features (e.g., the semantic model).
Having a draft available by the Ada-Europe 2009 meeting still appears achievable,
with the additional planned winter meeting.
Open SIs as of
SI-99-007 - Add support for new object oriented prefix notation
SI-99-019 - Add method to check if a name is an implicit dereference
SI-99-021 - Obtain representation clauses based on defining identifiers, not declarations
SI-99-024 - Provide a semantic model in addition to existing syntactic model
SI-99-033 - "=" for ASIS defined private types
SI-99-037 - Review std for problematic wording.
SI-99-038 - Generic units need to be included in Is_Body_Required
SI-99-039 - Change representation clauses to aspect clauses
SI-99-040 - Various questions
SI-99-041 - Adopt UTF-16 for ASIS
ISO/IEC TR 15942:2000, Guidance for the Use of Ada in High Integrity Systems, 22.15942, Brian Wichmann, Project Editor, supported by the Annex H Rapporteur Group.
This is a Type 3 Technical Report; it is publicly available.
JTC1/SC22 recommends to JTC1 that at the end of their 5-year review period, the following standards and technical report be confirmed: ISO/IEC TR 15942: 2000, Guidance for the use of Ada Programming Language in High-Integrity Systems.
Status: The request was forwarded to JTC1 for action during 2005. However, the result of their action is not evident. The convener has requested clarification.
No report.
ISO/IEC 18009:1999, Conformity Assessment of an Ada Language Processor, 22.18009, Erhard Ploedereder, Project Editor, supported by the Ada Rapporteur Group.
This document was "confirmed" by JTC1 in its 2004 systematic review.
No report.
ISO/IEC TR 24718:2005, Guide for the use of the Ada Ravenscar Profile in high integrity systems
22.24718, Alan Burns, Project Editor, supported by the Annex H Rapporteur Group
This is a Type 3 Technical Report providing guidance for users; it is publicly available.
No report.
WG9 [N406]: Procedures of the ARG
Resolution 44-4 of [N428]: The convener directs the chair of the ARG to send the list of AIs intended for submission to WG9 to NB and liaison representatives at the time they enter the 'editorial review' state. It would then be the duty of each NB and liaison representative to circulate this information within their own organization for the purpose of developing a position for the forthcoming meeting of WG9.
WG9 N464r, N468: Terms of reference and approach for the revision of ISO/IEC 15291 (approved by Resolution 50-7 [N470])
Resolution 50-6 of [N470]: Until otherwise directed by WG9, the ARG is requested to observe the following priorities in its work: (1, the highest priority) develop a revision of ISO/IEC 15291, ASIS; (2) respond to Defect Reports and/or Ada Issues on ISO/IEC 8652; (3) develop Technical Reports or Standards improving the Ada libraries--notably with respect to containers; and (4) consider proposals for extending the language.
WG9 requests that the ARG consider solutions to the problem described in comment 12 of N459 [containers], as well as other possible extensions to the standard library, and develop a New Work Item Proposal for a Type 2 Technical Report that will provide a "trial use" specification to users and implementers, and that will be suitable for future standardization.
Status: Open
From Minutes of Meeting #49 [N458]
While it is understood that the document delivered to WG9 is the Amendment document, the ARG, in compliance with resolution 48-3, is prepared to provide an integrated document (known in the vernacular as Reference Manual), and special care has been taken to ensure the consistency of these documents.
From Minutes of Meeting #49 [N458]
There was discussion of the appropriate scope of the revision: update enough
to permit access to the new
The amended document was retitled as "Approved Plan for the Revision of the ASIS Standard, ISO/IEC 15291" and renumbered as [N457].
|
Request from ARG |
The ARG Rapporteur posed the following question: Should it be permitted to select AIs of the amendment and implement them upon Ada 95? |
|
Discussion |
The ARG Rapporteur reported that there has been email discussion of applying some of the AIs of the amendment to the unamended language. It has been suggested that the AIs that constitute "corrections" or "clarifications" should be applied to old compilers. The Convener stated that AIs become part of the standard only when incorporated into a Corrigendum or an Amendment. AIs that are not incorporated but result in changing tests indicate only that the test was incorrect. Randy Brukardt (who operates the Ada Conformity Assessment Authority) noted that currently the ACATS suite is updated only for the Technical Corrigendum and has not been updated as a result of any AIs since then. As this is the operational test of conformity, it would not be possible to certify a compiler as conforming if it were to apply AIs processed since that date, but short of the full amendment. As a result of the discussion, the following resolution was approved. |
|
Resolution |
Resolution 49-7:WG9 recommends that all effort in enhancing the ACATS should be dedicated to tests appropriate for assessing conformance to Ada 2005. |
The ARG has its "usual" motion for the June meeting for approval of a series of AIs. See the list below. Pointers to retrieve the AIs are included. The list includes one Ada 95 AI: this is not a mistake; this AI makes it possible for existing compilers to support new Ada 2005 syntax in their Ada 95 implementation, in order to ease transition to the new language.
The cited AIs can be found online at http://www.ada-auth.org/AI-SUMMARY.HTML and http://www.ada-auth.org/AI05-SUMMARY.HTML.
AI95-00447-01/02 2006-06-16 -- Null_exclusions allowed in Ada 95
Ada 2005 AIs:
AI05-0007-1/03 2006-12-13 -- Stream 'Read and private scalar types
AI05-0014-1/02 2006-06-20 -- Accessibility of designated objects
AI05-0015-1/03 2006-12-13 -- Constant return objects
AI05-0016-1/02 2006-12-13 -- Others => <> can be used in place of null record
AI05-0020-1/02 2006-12-13 -- Universal operators of fixed point and access types
AI05-0021-1/02 2006-12-13 -- Issues with containers
AI05-0025-1/02 2006-12-13 -- Missing legality rules for formal_package_association
The ARG has approved of a series of AIs. See the list below.
The cited AIs can be found online at http://www.ada-auth.org/AI-SUMMARY.HTML and http://www.ada-auth.org/AI05-SUMMARY.HTML.
AI05-0002-1/04 2007-10-01 -- Unconstrained arrays and C interfacing
AI05-0008-1/05 2007-10-01 -- General access values that might designate constrained objects
AI05-0017-1/04 2007-10-01 -- Freezing and incomplete types
AI05-0019-1/04 2007-10-01 -- Primitive subprograms are frozen with a tagged type
AI05-0024-1/05 2007-10-01 -- Run-time accessibility checks
AI05-0028-1/06 2007-10-01 -- Problems with preelaboration
AI05-0035-1/04 2007-10-01 -- Inconsistences with
pure units
AI05-0037-1/02 2007-10-08 -- Out of range <> associations in array
aggregates
AI05-0040-1/03 2007-10-08 -- Limited with clauses on descendants
AI05-0043-1/02 2007-10-08 -- The Exception_Message for failed language-defined checks
AI05-0046-1/03 2007-10-08 -- Null exclusions must match for profiles to be
fully conformant
AI05-0055-1/03 2007-10-08 -- Glitch in EDF protocol
AI05-0056-1/02 2007-06-17 -- Wrong result for Index functions
The ARG completed discussion of a substantial number of AI's, and moved to submit them to the WG9 June meeting for approval. The list is below. Pointers to retrieve the AIs are included.
The cited AIs can be found online at http://www.ada-auth.org/AI-SUMMARY.HTML.
AI05-0004-1/12 2008-05-15 -- Presentation issues in the Standard
AI05-0013-1/13 2008-05-21 -- No_Nested_Finalization is difficult to enforce
AI05-0022-1/04 2008-04-09 -- Container tampering should be checked for formal subprograms
AI05-0023-1/06 2008-04-09 -- 'Read on records with variant parts
AI05-0026-1/04 2008-04-09 -- Missing rules for Unchecked_Unions
AI05-0027-1/06 2008-05-15 -- Behavior of container operations when passed a finalized container object
AI05-0029-1/04 2008-04-21 -- Operations that are not declared but still exist
AI05-0030-2/04 2008-04-21 -- Requeue on synchronized interfaces
AI05-0032-1/02 2007-11-11 -- Extended return statements for class-wide functions
AI05-0033-1/04 2008-05-21 -- Rules for non-library level interrupt handlers
AI05-0034-1/04 2007-11-26 -- Categorization of limited views
AI05-0036-1/01 2007-01-18 -- Number of characters to be output for Text_IO for enumerations
AI05-0038-1/03 2007-11-26 -- Minor Errors in Ada.Text_IO.
AI05-0039-1/04 2008-05-15 -- User-defined stream attributes cannot be dynamic
AI05-0041-1/08 2008-05-15 -- Derived types and partial views
AI05-0042-1/04 2008-05-21 -- Overriding versus implemented-by
AI05-0044-1/04 2008-05-15 -- Equivalence and equality in containers
AI05-0045-1/05 2008-04-21 -- Termination of unactivated tasks
AI05-0047-1/07 2008-05-27 -- Annoyances in the array packages
AI05-0048-1/03 2008-04-21 -- Redispatching is not expected in language-defined subprograms
AI05-0058-1/01 2007-08-01 -- Abnormal completion of an extended return statement
AI05-0060-1/07 2008-05-21 -- The definition of Remote access types is too limiting
AI05-0062-1/03 2008-04-18 -- Null exclusions and deferred constants
AI05-0064-1/01 2007-09-13 -- Redundant finalization rule
AI05-0065-1/03 2008-04-18 -- Remote access types should be defined as externally streamable
AI05-0066-1/05 2008-05-21 -- Temporary objects are required to live too long
AI05-0068-1/03 2008-04-18 -- Inherited subprograms may be both abstract and require overriding
AI05-0070-1/01 2007-10-24 -- Elaboration of interface types
AI05-0072-1/02 2007-12-13 -- Termination only signals 'Terminated when it is True
AI05-0073-1/04 2008-04-18 -- Questions about functions returning abstract types
AI05-0076-1/03 2008-04-18 -- Meaning of "function with a controlling result"
AI05-0077-1/03 2008-04-18 -- The scope of a declaration does not include any context clause
AI05-0078-1/03 2008-04-18 -- Alignment need not match for Unchecked_Conversion
AI05-0079-1/04 2008-05-21 -- An other_format character should be allowed wherever a separator is allowed
AI05-0080-1/04 2008-05-21 -- "view of" is not needed when it is clear from context
AI05-0082-1/03 2008-04-18 -- Accessibility level of generic formal types
AI05-0084-1/03 2008-04-18 -- Pragma Remote_Types for Container library units
AI05-0086-1/02 2008-04-18 -- Statically compatible needs to take null exclusions into account
AI05-0087-1/03 2008-04-18 -- Formal nonlimited derived types should not have limited actual types
AI05-0088-1/01 2008-01-30 -- Only the value of "**" is equivalent to repeated "*"s
The ARG met in
Work on the ASIS document is proceeding, albeit more slowly than planned. The most significant item of work is still the proposed semantic interface, that is intended to provide a higher-level set of primitives to the ASIS programmer than the current syntax-oriented queries. Preliminary versions of the new interface have been presented by Tucker Taft, and a test case has been proposed, for an application for which an ASIS95 version already exists. In addition, several updates to the current standard, involving Ada 2005 features, have been incorporated into the new ASIS draft.
At the
The cited AIs can be found online at http://www.ada-auth.org/AI-SUMMARY.HTML and http://www.ada-auth.org/AI05-SUMMARY.HTML
AI05-0006-1/06 2008-07-07 -- Nominal subtypes for all names
AI05-0052-1/11 2008-10-22 -- Coextensions and distributed overhead
AI05-0053-1/06 2008-05-27 -- Aliased views of unaliased objects
AI05-0063-1/05 2008-07-07 -- Access discriminants on derived formal types
AI05-0071-1/05 2008-10-22 -- Class-wide operations for formal subprograms
AI05-0083-1/04 2008-10-21 -- Representation values of formal parameters
AI05-0090-1/05 2008-10-21 -- Ambiguities with prefixed views of synchronized primitives
AI05-0091-1/03 2008-10-18 -- An other_format character is not allowed in an identifier
AI05-0093-1/03 2008-10-18 -- Additional rules that need to use "immutably limited"
AI05-0094-1/03 2008-10-18 -- Timing_Events should not require deadlock
AI05-0096-1/04 2008-10-18 -- Deriving from formal limited types
AI05-0097-1/03 2008-10-18 -- 3.9.3(4) includes abstract null extensions
AI05-0098-1/03 2008-10-18 -- Incomplete type names can be used in anonymous access-to-subprogram types
AI05-0104-1/02 2008-07-07 -- Null exclusions are not allowed in uninitialized allocators
AI05-0105-1/02 2008-07-03 -- Resolution of renames uses anonymousness
Resolution 55-4 Resolution 55-8
WG9 N416, Charter of the HRG
From the Minutes of Meeting #49 [N458]
The HRG has not met since the last meeting of WG9. It has reviewed (by
email) its future agenda and has decided that it should revisit the Guidelines
for use of
From the Minutes of Meeting #49 [N458]
Both Steve Michell and Erhard Ploedereder stated
that they planned to participated in OWG:Vulnerability
representing
Received from A. Burns,
Received from A.
Burns,
My apologies for not attending the forthcoming meeting
A short report from the HRG:
There has been no meetings or actions since the last meeting of WG9. However the
HRG is preparing to take on the task of producing the Ada-specific Annex to the
OWG-V report. We expect to be able to start this work following the forthcoming
meeting of OWG-V (WG23) on 29/9 - 1/10.
PRG Report to WG9
The PRG was created at SC22/WG9 meeting 51,
To date I have not called a meeting of the full PRG. An email reflector has been created at
posix-ada-comment@ada-auth.org
I have created a draft set of procedures from the ARG procedures. I can present them to WG9, but since a PRG meeting has not considered them, I think this is premature.
I have worked with Randy Brukhardt to set up a web-site similar to ada-auth.org, but this work is still in its beginnings.
I have met with Ted Baker, Brad Moore and Luke Wong in an informal review of IS14519. This "informal" meeting happened 19-21 February 2007 at Ted's locale and was a 3-day review of the existing document and a Canadian contribution that we prepared in Oct and Nov 2006. From this meeting we have a list of items that need likely attention. It is a large list, but many of the items can likely be dealt with directly. One of the issues that we would need to come to terms with is if we treat these as AI's are treated, can we lump them into a few larger PI's or will we need a plethora of PI's. My intention is to call a meeting and use this list as a starting point for discussions.
From this meeting and subsequent events I can report:
• Ted is willing to continue as editor, but has no financial resources to put to this task.
• Luke Wong was intending to volunteer as Rapporteur. This looks like it will not happen, which leaves me in a challenging position. My workload (and no funding) is one of the reasons why more progress has not been made.
• The standard needs updating, at least minimally. We reviewed most of the significant decisions from the earlier binding activities and believe that they are still correct, such as not implementing access to POSIX features that conflict with Ada-provided services, such as task (or thread) management, or IO, or not implementing services that were too large and troublesome, such as System V material, logging, etc. The main issues that need attention are those from mistakes in the current binding and changes because of new POSIX errors, symbols, and new capabilities in services that we already provide.
• There is some interest in seeing this standard progressed, but to date we have not found anyone wanting to fund one or more of us to do the work. That being said, if this is an all-volunteer effort it will run at a minimal rate.
Received from Stephen Michell,
Report to WG9 on status of Ada-POSIX Binding Investigation
Stephen Michell, Rapporteur PRG, November 2007.
Project: Revision of ISO/IEC 14519:1998 Ada POSIX Binding
Calling meeting for Feb 6-8 in
willing to host us 6-8 Feb. Hopefully we can overlap with ARG for Friday morning.
Analysed existing Ada POSIX Binding document, 9945:2008(Draft) to identify
What is still valid
What we don't want to include
(c-specific, already in Core Ada or in Annexes)
Parts that have been obsoleted by 9945 since 1996
(and there are quite a few)
Developed list of issues - about 1800 individual data points and categorized them.
A small group (Michell, Moore,
Wong) met in
analysis, reasons and to gain his perspective on various issues.
What we are left with is a set of approximately 350 individual datapoints that need further analysis. These have a significant variety of reasons for needing further analysis. Most will be solved by a careful review and a change of a name or just a POSIX reference in the document. A few might need new the possible addition of new procedures, constants or types. A very few could require new packages and functionality defined.
We have a plan to develop a web site in parallel with ada-auth.org mainitained by Randy Brukhart, and to develop a few POSIX Issues.
POSIX Issues
We predict only a small number (20-50) POSIX Issues needed to capture analysis done or to be done.
PRG Interest
There is a group of about 10 people that have expressed interest in the activity. An email reflector has been set up but has not been used much yet. (need web site to support the activity).
PRG Procedures
I have prepared a set of procedures for presentation and review at the first meeting. This document came from ARG procedures. I expect that some simplification will occur.
Standardization
The final product needs IEEE and ISO/IEC/JTC1 approval processes. This may govern the final product. Ideally an amendment or even a technical corrigendum might be possible, if IEEE agrees. We (Ted) asked IEEE to waive copywright but have had no response.
Austin Group has offered to help, but in non-technical ways. I expect that they could be used for sanity checks and to help navigate the EEE balloting processes.
Workload
The amount of work to be done probably translates to about 1 person years of work. Since we are unfunded, 5 or 6 people over 2 years could probably do this work.
Officers
It seems as though I should stay on as Rapporteur. My heavy workload interferes with progress, but given the lack of interest of anyone else wanting to lead this effort, it seems like the best alternative. Ted Baker has agreed to stay involved as editor. Given Ted's expertise and knowledge of the toolset in producing the document, this will also minimize our effort.
Report to WG9 on status of Ada-POSIX Binding Investigation
Stephen Michell, Rapporteur PRG, June 2008.
Project: Revision of ISO/IEC 14519:1998 Ada POSIX Binding
Officers:
Stephen Michell, Rapporteur
Ted Baker, Editor
Membership: Stephen Michell, Ted Baker, Luke Wong, Canada, Brad Moore, Canada, Matt Gingell, USA, Michael Gonzales-Harbour, Spain, some on internet as observers.
Future meetings:
• Monthly teleconferences July - Nov 2008
•
•
• June
2009 in
Meeting 2-4 Feb 2008
Discussed PRG Procedures document. The document discusses the way that PIs
are discussed, but not how the standard itself is dealt with. The document does
not include IEEE maintenance issues. We probably need to make this a joint
maintenance committee and figure out how to make this work. Steve and Ted have
an action Item to discuss with IEEE how a standards group can be organized.
Discussed various approaches for standardization. The largest challenge is the IEEE balloting effort, as it would seem that we are unlikely to build the balloting membership with the proper mix of vendors, users, acedemia to carry a successful ballot. We have tried to identify IEEE officers to help us examine alternative approaches, but have no responses to any queries for information. I have also been thinking that ISO could use their copywrite to unilaterally issue an amendment to the document, but need to hold discussions with ITTF and the JTC1 secretariat to determine feasibility of such an approach.
We took the list of issues developed in 2007 and developed 22 PI's. These PI's are a statement of the issue
and a collation of the issues collected.
Each PI was assigned to a member to develop a primary writeup,
analysis and proposed approach. In many cases the proposed approach will be no
action (since the
Meeting 15-16 June 2008
A small subset met in
Although the PRG web site is up, no PI's have been placed on this site, due to the immaturity of the issues identified and lack or writeups.
Progress has been slower than I want, and we are not getting the attendance
necessary. I have therefore proposed holding the next meetings by monthly phone
conferences, with a goal to push the generation and review of PI's. A full PRG
meeting is planned for
Developed list of issues - about 1800 individual data points and categorized them.
POSIX Issues
We predict only a small number (30-40) POSIX Issues needed to capture analysis done or to be done.
PRG Interest
There is a group of about 10 people that have expressed interest in the activity. An email reflector has been set up but has not been used much yet. (need web site to support the activity).
PRG Procedures
I have prepared a set of procedures for presentation and review at the first meeting. This document came from ARG procedures. We need to include more focus on standardization.
Standardization
The final product may need IEEE and ISO/IEC/JTC1 approval processes. This may govern the final product. Ideally an amendment or even a technical corrigendum might be possible, if IEEE agrees. We (Ted) asked IEEE to waive copyright but have had no response.
Austin Group has offered to help, but in non-technical ways. I expect that they could be used for sanity checks and to help navigate the IEEE balloting processes, if we use this process.
Work Item:
We should not need to create an NP for maintenance or development of a TC. At this point we would fail the requirement for 5 countries but could likely add some supporting folks.
Workload:
The amount of work to be done probably translates to about 1 person years of work. Since we are unfunded, 5 or 6 people over 2 years could probably do this work.
Received from
Report to WG9 on status of Ada-POSIX
Binding Investigation
Stephen
Michell, Rapporteur PRG, June 2008
Project: Revision of ISO/IEC
14519:1998 Ada POSIX Binding
Officers:
Stephen Michell, Rapporteur
Ted Baker, Editor
Membership:
Stephen Michell, Canada
Ted Baker, SIGAda
Luke Wong, Canada
Brad Moore, Canada,
Ron Price, SIGAda
Matt Gingell, USA, Adacore,
Michael Gonzales-Harbour, Spain,
Some on internet as observers.
Future meetings
Monthly teleconferences Nov -
Feb 2009
Meeting Oct 29, 2008 Oregon
We decided to have a fixed teleconference the
first Wednesday of each month from 2030-2130 EST (or EDT), followed by Feb
meeting in
PI 0001, 0008, 0015, 0021 for discussion 12 Nov mtg.
Belgium, Canada, France, Italy, the United Kingdom, and the United States submitted position statements as part of their National Body reports. An individual from Germany has offered an opinion that is believed to reflect the position of the German National Body.
Conversation and email exchanges with the SC22 provided the following
insight:
How many corrigenda does the standard currently have? If WG9 wants to capture any changes before the
new edition, we’ll need to do another corrigenda. Then we’ll request that a new
edition be published which incorporates the amendment and two corrigenda. We don’t
have to do a full revision if we do not wish to, but the new edition will only
capture already agreed to changes in the amendment and corrigenda, and nothing
new.
Generally, speaking the consensus is that effort should be taken to develop a single integrated document of the standard, amendment, and corrigenda. There is concern about the magnitude and expense of a new revision.
Steps should be taken to generate a new amendment that captures the AIs and improvements to the current instantiation of the
language. Following the approval of this
amendment, the US
Overall the scope of the work on the Technical Corrigenda should be:
· Modest -- the intent is that the change is small enough that we can continue to call it Ada 2005 (its too soon for another earthquake-sized change);
· Encapsulation of Containers – the intent is to include the previously separate containers project;
· Efficient – the intent is to deliver the final document to WG 9 before the end of 2010.
There is some concern over the copyright on the new editions and amendments.
The Convener will investigate when the New Work Item should be initiated for the Amendment. Expect that it will take about two years to create the new amendment.
WG9 instructs the ARG to develop the content and schedule for a new Amendment.
At the last meeting of WG9, the HRG
was tasked to develop an Annex to the OWG/WG23 Report on Vulnerabilities that
addresses
HRG is tasked to develop the annex to the OWG/WG23 Technical Report (TR). However, there needs to be a wider forum for the membership of WG9 to comment on the content of the OWG/WG23 TR. WG9 needs to develop a coordinated response on the overall OWG/WG23 TR. Comments on the current version are needed early in the 2009.
Notes on TR review. Erhard showed some example subsections of WG23 document;
it is not hard to review (currently 127 pages, but only about 60 pages with
actual content to be edited); responses must be returned in an MS Excel
spreadsheet.
When the Convener receives the TR from SC22, it will be distributed to the
following National Bodies for review and comment:
The National Bodies will have 30 days to review and respond. Within 10 days of receiving all responses, the Convener will consolidate the reviews and send the position statement out to the National Bodies for confirmation. The National Bodies will have 30 days to reply. The Convener will submit the final confirmed position to SC22 as the WG9 position.
A proposal to have a workshop on the OWG/WG23 TR at the next session of Ada-Europe 2009 and SIGAda 2009 has been submitted. A presentation of the basic concept of vulnerabilities should also be conducted at these events.
WG9 shall develop a coordinated response on the overall OWG/WG23 Technical Report when it is received from SC22.
We appreciate the comfortable accommodations provided by SIGAda. The resolution expresses WG9's gratitude.
We appreciate the services of the meeting Secretary, Clyde Roby. The resolution expresses WG9's gratitude.
We appreciate the continuing services of the WG9 Web Master, Clyde Roby. The resolution expresses WG9's gratitude.
WG9 instructs the ARG to develop the content and schedule for a new Amendment.
WG9 shall develop a coordinated response on the overall OWG/WG23 Technical Report when it is received from SC22.
The minutes of Meeting #54 are contained in document N490 are approved.
ISO/IEC JTC1/SC22/WG9 continues its Ada Rapporteur Group until the next plenary meeting and expresses its grateful appreciation to the Rapporteur and the members for their continuing service.
Ed Schonberg (US) is continued as Rapporteur.
The membership of the ARG is designated to be: Steve Baird (SIGAda), John Barnes (UK), Randy Brukardt (US), Alan Burns (UK), Robert Dewar (US), Gary Dismukes (US), Robert Duff (US), Kiyoshi Ishihata (Japan), Bibb Latting (US), Pascal Leroy (France), Brad Moore (Canada), Erhard Ploedereder (Ada-Europe), Jean-Pierre Rosen (France), Ed Schonberg (US), Tucker Taft (US), Bill Thomas (SIGAda), and Tullio Vardanega (Italy).
The Convener of WG9 is authorized to act for WG9 between meetings in
appointing additional members of the
Rapporteurs are permitted to allow other individuals to observe the deliberations of the Rapporteur Group. The admission of observers and the extent of participation permitted to observers are at the discretion of the Rapporteur with the concurrence of the membership of the Rapporteur Group.
ISO/IEC JTC1/SC22/WG9 continues its Annex H Rapporteur Group until the next plenary meeting and expresses its grateful appreciation to the Rapporteur and the members for their continuing service.
Alan Burns (UK) is continued as Rapporteur.
The membership of the HRG is designated to be: John Barnes (UK), Patrick de Bondeli (France), Alan Burns (UK), Rod Chapman (UK), Robert Dewar (US), Bob Duff (US), Michael Holloway (SIGAda), Stephen Michell (Canada), Michael Pickett (UK), Erhard Ploedereder (Ada-Europe), Juan Antonio de la Puente (Ada Europe), George Romanski (SIGAda), Jean-Pierre Rosen (France), Mark Saaltink (Canada), Tullio Vardanega (Italy), and Brian Wichmann (UK).
The Convener of WG9 is authorized to act for WG9 between meetings in appointing additional members of the HRG. In doing so, she shall consult with the Rapporteur and the National Body or Liaison Organization nominating the member.
Rapporteurs are permitted to allow other individuals to observe the deliberations of the Rapporteur Group. The admission of observers and the extent of participation permitted to observers are at the discretion of the Rapporteur with the concurrence of the membership of the Rapporteur Group.
ISO/IEC JTC1/SC22/WG9 continues its POSIX/Ada binding Rapporteur Group (PRG) until the next plenary meeting and expresses its grateful appreciation to the Rapporteur and the members for their continuing service.
Stephen Michell(
The membership of the PRG is designated to be: Ted Baker (SIGAda), Matt Gingell (US), Michael Gonzalez-Harbour
(
The Convener of WG9 is authorized to act for WG9 between meetings in appointing additional members of the PRG. In doing so, she shall consult with the Rapporteur and the National Body or Liaison Organization nominating the member.
Rapporteurs are permitted to allow other individuals to observe the deliberations of the Rapporteur Group. The admission of observers and the extent of participation permitted to observers are at the discretion of the Rapporteur with the concurrence of the membership of the Rapporteur Group.
WG9 schedules future meetings as follows:
WG9 approves the following AIs, which have been previously approved by the ARG:
AI05-0006-1/06 2008-07-07 -- Nominal subtypes for all names
AI05-0052-1/11 2008-10-22 -- Coextensions and distributed overhead
AI05-0053-1/06 2008-05-27 -- Aliased views of unaliased objects
AI05-0063-1/05 2008-07-07 -- Access discriminants on derived formal types
AI05-0071-1/05 2008-10-22 -- Class-wide operations for formal subprograms
AI05-0083-1/04 2008-10-21 -- Representation values of formal parameters
AI05-0090-1/05 2008-10-21 -- Ambiguities with prefixed views of synchronized primitives
AI05-0091-1/03 2008-10-18 -- An other_format character is not allowed in an identifier
AI05-0093-1/03 2008-10-18 -- Additional rules that need to use "immutably limited"
AI05-0094-1/03 2008-10-18 -- Timing_Events should not require deadlock
AI05-0096-1/04 2008-10-18 -- Deriving from formal limited types
AI05-0097-1/03 2008-10-18 -- 3.9.3(4) includes abstract null extensions
AI05-0098-1/03 2008-10-18 -- Incomplete type names can be used in anonymous access-to-subprogram types
AI05-0104-1/02 2008-07-07 -- Null exclusions are not allowed in uninitialized allocators
AI05-0105-1/02 2008-07-03 -- Resolution of renames uses anonymousness
ISO/IEC JTC1/SC22/WG9 expresses its grateful appreciation to SIGAda for their gracious accommodations in hosting Meeting #55.
ISO/IEC JTC1/SC22/WG9 expresses its grateful appreciation to Clyde Roby for serving as Secretary of Meeting #55.
ISO/IEC JTC1/SC22/WG9 expresses its grateful appreciation to Clyde Roby for his continuing service in maintaining the WG9 Web Page.
The meeting ended at
N388, Request for Subdivision of Project ISO/IEC 8652:1995
N389,
Minutes, Meeting #40 of ISO/IEC JTC1/SC22/WG9,
N404, Working Draft, Revision of ISO/IEC 13813
N405, Recommendation on ISO/IEC 13813 from the
N406, Procedures of the Ada Rapporteur Group
N412, Instructions to the Ada Rapporteur Group from SC22/WG9 for
Preparation of the Amendment to ISO/IEC 8652,
N414, Notification of Approval of Category C Liaisons between SC22/WG9 and Ada-Europe and SIGAda
N416, Charter of the Annex H Rapporteur Group (HRG)
N417, Charter of the ASIS Rapporteur Group (ASISRG)
N423, Convener's Comments on Instructions to the Ada Rapporteur Group from SC22/WG9 for Preparation of the Amendment to ISO/IEC 8652, December 2002
N424,
N426, Proposed New Work Item, Guide for the use of the Ada Ravenscar Profile in High-Integrity Systems
N428r,
Minutes, Meeting #44 of ISO/IEC JTC1/SC22/WG9,
N435, Draft for PDTR Approval Ballot, ISO/IEC TR 24718, Guide for the
use of the Ada Ravenscar Profile in high integrity
systems,
N437, ARG Rapporteur's Proposal for Defining
Scope of Amendment to ISO/IEC 8652:1995,
N441, SC22 N3758, WG9 Request for National Body Contributions on
Implementation of Coded Character Sets in
N442, Draft submitted for DTR Approval Ballot, ISO/IEC TR 24718, Guide
for the use of the Ravenscar Profile in high
integrity systems,
N444, Meeting Report: ISO/IEC JTC1/SC22, 6-10 September 2004, Jeju,
N445, DRAFT Explanatory Report re SC22 Resolution 04-15
N447, Explanatory Report re SC22 Resolution 04-15
N452r, Convener's Report, 2005, ISO/IEC JTC1/SC22/WG9 (
N454, Meeting Report: ISO/IEC JTC1/SC22 (Programming Languages,
Operating Systems and Environments), 29 September to
N456, Convener Proposal for the Revision of the ASIS Standard, ISO/IEC 15291
N457, Approved Plan for the Revision of the ASIS Standard, ISO/IEC 15291
N458,
Minutes, Meeting #49 of ISO/IEC JTC1/SC22/WG9,
N459, Disposition of Informal Comments Received on Editor's Draft of
Amendment,
N460, Editor's Draft, Amendment 1 to ISO/IEC 8652, March 2006
N462, JTC1 Directives, 5th edition, Version 2, April 2006 (JTC001-N-8122)
N463, ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards
N464r, 2nd Preliminary draft New Work Item Proposal for the Revision of ISO/IEC 15291, ASIS
N465, Response of ISO/IEC JTC1/SC22/WG9 to SC22 Resolution 5-15
N467, Submission of ISO/IEC 8652:1995/FPDAM 1 to SC22 for FPDAM ballot
N468, Example approach for structuring the revised ASIS Standard
N469, John Benito, "OWG: Vulnerability -- A new type of Working
Group used for a new SC22 Working Group," for SC22/WG9 Meeting,
N470,
Minutes, Meeting #50 of ISO/IEC JTC1/SC22/WG9,
N472, Proposal to Revise ISO/IEC 15291, Information technology - Programming languages - Ada Semantic Interface Specification (ASIS)
N475, Meeting Report: Plenary Meeting of ISO/IEC JTC 1/SC 22, 18-22
September 2006,
N477, Canadian Contribution, Initial Work Scope Summary for updating Ada POSIX Bindings IS 14519:2001 to POSIX Draft IS 9945:2008 and Ada 2005.
N479, SIGAda
contribution, Clyde Roby, Notes of Birds-of-a-Feather session on POSIX-Ada
Binding, conducted at SIGAda 2006,
N480,
Announcement and Draft Agenda, Meeting #52 of ISO/IEC JTC 1/SC 22/WG 9,
N481, Draft
Detailed Agenda, Meeting #52 of ISO/IEC JTC 1/SC 22/WG 9,
N482,
Draft Minutes, Meeting #52 of ISO/IEC JTC 1/SC 22/WG 9,
N483,
Annual Convener's Report, 2007, ISO/IEC JTC1/SC22/WG9 (
N484,
Announcement and Draft Agenda, Meeting #53 of ISO/IEC JTC1/SC22/WG9, Thu,
N485, Detailed
Agenda, Meeting #53 of ISO/IEC JTC 1/SC 22/WG 9,
N486,
Draft Minutes, Meeting #53 of ISO/IEC JTC 1/SC 22/WG 9,
N487,
Announcement and Draft Agenda, Meeting #54 of ISO/IEC JTC1/SC22/WG9,
N488,
Draft Detailed Agenda, Meeting #54 of ISO/IEC JTC 1/SC 22/WG 9,
N489, OWGV Summary 2008
N490,
Minutes, Meeting #54 of ISO/IEC JTC1/SC22/WG9,
N491,
Convener's Report, 2008, ISO/IEC JTC 1/SC 22/WG 9 (
N492,
Announcement and Draft Agenda, Meeting #55 of ISO/IEC JTC 1/SC 22/WG 9,
ISO Web Site: http://www.iso.org/
ITTF Web site of publicly available standards: http://isotc.iso.ch/livelink/livelink/fetch/2000/2489/Ittf_Home/PubliclyAvailableStandards.htm.
JTC1 Web Site: http://www.jtc1.org/
SC22 Web Site: http://www.open-std.org/JTC1/SC22/
WG9 Web Site: http://www.open-std.org/JTC1/SC22/WG9/
SC22 High Integrity Ad Hoc Group Web Site: http://www.aitcnet.org/isai/
ACAA Web Site: http://www.ada-auth.org/
ACAA Web Site for ARG Minutes: http://www.ada-auth.org/arg-minutes.html
ACAA Web Site for AIs: http://www.ada-auth.org/cgi-bin/cvsweb.cgi/AIs/
ACAA Web Site for Amendment: http://www.ada-auth.org/amendment.html
Ada-Europe Web Site: http://www.ada-europe.org/
Ada-Europe 2008 Conference Web Site: http://www.ada-europe.org/conference2008.html
SIGAda Web Site: http://www.acm.org/sigada/
SIGAda 2008 Conference Web Site: http://www.sigada.org/conf/sigada2008/
OWG: Vulnerabilities Site: http://www.aitcnet.org/isai/
[Agenda]
End of Document