1 / 9

Ada Programming Group Recommendations for Improvement

Recommendations from the ALIOOOP and IRONMASC groups regarding interfaces, type stubs, CPU accounting, distribution, safety area, and assertion facilities in Ada programming. Addressing issues of high and medium importance, proposing solutions and discussing potential enhancements.

iokina
Download Presentation

Ada Programming Group Recommendations for Improvement

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WG9 Forum Results Clyde Roby, SIGAda Presented to ISO/WG9 December 13, 2002

  2. ALIOOOP Group • Issues of High Importance • Interfaces • Type stubs or equivalent – mutually dependence • Object-Oriented syntax (tagged types only, e.g., “Object.Method”) • Pragma for requiring local variables to be initialized • Checking for physical units (physics, chemistry, etc.)

  3. ALIOOOP Group • Issues of Medium Importance • Access Type conversion – implicit instead of explicit • Limited types being less limited – aggregates and then function return • Pre/Post Assertions

  4. IRONMASC Task • CPU Accounting – High • TCB attribute (make API?) • Pay attention to CMK’s four annexes • Need to insert provisions for bare machines for configuring scheduler and loosen some remarks

  5. IRONMASC Task • Distribution – what to do? • Can we do something about Global Time? – issue about how to synchronize clock (for all such protocols, it’s doable, but might be hard) • Nobody uses the Distributed Systems Annex • Need multiple clocks for fault tolerance, then will drift – need to keep them in synch • DSA (programmatic distribution) better than CORBA (needs lower primitives) • Shared memory is highly complex, but Ada works

  6. IRONMASC Task • Safety Area – what is desired? • Standardized set of restrictions • Predefined libraries • Style check by compiler (can be done with a separate tool using ASIS) • Will OO affect real-time?

  7. IRONMASC Task • Assertion Facility • Distinguish dynamic assertions done that is intended versus effort of “design by contract” (static) • Static case – for every significant issue • Dynamic case – for simpler issues • Units problem – want a good solution

  8. IRONMASC Task • Dynamic mechanism • Simple but issue with function side effects • Static mechanism • Involves quality predicate logic outside realm of compiler technology today • Maybe put in an optional Annex? • Comparable static assertion OK

  9. IRONMASC Task • Common Criteria • Wipe memory clean when deallocated or stack popped – pragma? • Simpler syntax for Unchecked Conversion • pragma ReadOnly (object) • Shift operator for modular types

More Related