From cooper@longshot.ds.boeing.com Wed Feb 18 19:09:05 1998 Return-Path: Received: from cs.ida.org by cronus.csed.ida.org (SMI-8.6/SMI-SVR4) id TAA05944; Wed, 18 Feb 1998 19:09:04 -0500 Received: from mail.acm.org (mail.acm.org [199.222.69.4]) by cs.ida.org (8.8.7/8.8.7) with ESMTP id TAA19266 for ; Wed, 18 Feb 1998 19:10:17 -0500 (EST) Received: from sw-eng.falls-church.va.us (ns1.sw-eng.falls-church.va.us [199.75.54.2]) by mail.acm.org (8.8.5/8.7.5) with ESMTP id TAA36280; Wed, 18 Feb 1998 19:09:01 -0500 Received: from mailgate2.boeing.com by sw-eng.falls-church.va.us (8.8.8/) id AAA19232; Thu, 19 Feb 1998 00:05:42 GMT Received: from splinter.boeing.com ([130.42.28.12]) by mailgate2.boeing.com (8.8.5/8.8.5) with ESMTP id QAA23151 for ; Wed, 18 Feb 1998 16:09:17 -0800 (PST) Received: from longshot.ds.boeing.com by splinter.boeing.com with ESMTP (1.37.109.16/16.2) id AA035176957; Wed, 18 Feb 1998 16:09:17 -0800 Received: by longshot.ds.boeing.com (SMI-8.6/SMI-SVR4) id QAA20009; Wed, 18 Feb 1998 16:09:14 -0800 Date: Wed, 18 Feb 1998 16:09:14 -0800 From: cooper@longshot.ds.boeing.com (C. Daniel Cooper) Message-Id: <199802190009.QAA20009@longshot.ds.boeing.com> To: ASIS-officers@sw-eng.falls-church.va.us, tom@xavier.ds.boeing.com, stan@forge.ds.boeing.com Subject: ASIS ease of use Cc: maretta@longshot.ida.org, bobl@longshot.ida.org X-Sun-Charset: US-ASCII Content-Length: 4742 Status: OR Currie, > Great! This will probably be the outcome, pending negative comments. By > the way, Sergey has generated the following extensions: > > function Is_Dispatching_Call (Call : Asis.Element) > return Boolean; > function Is_Dispatching_Operation (Declaration : Asis.Element) > return Boolean; > function Acts_As_Spec (Declaration : Asis.Element) > return Boolean; > function Is_Renaming_As_Body (Declaration : Asis.Element) > return Boolean; > function Components (E : Asis.Element) > return Asis.Element_List; > > Presumeably we might want to include Is_Dispatching_Operation as well? > Thoughts? Actually, I like *all* of the above. > Depending on the issues raised for the ASIS Final CD Ballot, we may need > a meeting for their resolution. I am currently anticipating we can > resolve all the issues via email. Perhaps we might want to consider a > meeting in early April dedicated to resolving issues and taking the > first step towards identifying secondary queries. If most of the ASIS > Final CD Ballot issues become resolved before the meeting then the > meeting can devote its entirity to the secondary queries. Like last year, I'll be available March 21-29; maybe DDC-I (Joyce Tokar) would like to host us again :-) > Otherwise, I fear ASIS will only see light > in (many fewer) development groups, who have made a large investment > in building Ada tools. Without a useful set of tool-oriented higher- > level queries, I see the broader, casual, lightweight use of ASIS > never really materializing, relegating ASIS to an arcane specialty. To underscore the above concern, here's a comment from Dan Ehrenfried: : As a note, in the years that Rational offered the LRM_interfaces, : I can remember less that 5 customers who seriously tried to do this : kind of analysis. Rational technical people did most of this kind of : customization programming. So the interfaces were used in this way, : but not by the general populace. I don't think ASIS must necessarily suffer the same fate; but we still have some way to go, to make ASIS sufficiently easy to use for ordinary engineers. > Incidently, Dan has been pushing me on this issue for a long time. I > wanted to keep the focus on the ASIS specification. The ASIS > specification is practically in auto drive so it is time to address the > secondary queries. The fact that ASIS for GNAT already has identified 5 > secondary queries indicates that this is an important area to focus. I have been asking our engineers who try ASIS to keep a list of features they expected but that are missing. So far, most are along the lines of: multiple ways of outputting names (fully qualified or not, capitalized or not, uniqueness markers for overloaded names, etc) and other string management utilities; a higher-level "framework" for canonical traversal (I believe Bill Thomas is working on an example of this); iterators and list management utilities; etc. Interestingly, another major area for improvement does not require new secondary queries at all, but rather involves better/more user-oriented examples/documentation/tutorials. For example, one user I talked to had complaints about the tedium of locating the context after landing on a specific element of interest -- a bottom-up approach; later, he realized he could simply cache this in passing, as the traversal zeroed in on the element. The implicit top-down nature of the traversal had simply eluded him in the Appendix B examples he had started from. And even expert users can experience surprises: we had a recent case where Dan Ehrenfried's Ada Analyzer did not recognize T'First to be the same thing as T'first (ie, case sensitivity). Gary Barnes responded: : To make a long story short, Diana uppercases everything so the two forms : should be equivalent. The ASIS program can make calls either to read the : Diana (correct) or to read the text image of the attribute (incorrect). : Ada Analyzer should do the former but it appears to be doing the latter. ...and indeed, it turned out that the tool was working from the text image (which was capitalized inconsistently) rather than using the attribute designator name. Good user manuals should go a long way towards helping *all* users succeed with ASIS. -- C. Daniel Cooper ==========v=======================. Adv Computing Technologist | All opinions are mine | 206-655-3519 | and may not represent | CDaniel.Cooper@Boeing.com | those of my employer. | ---------------------------^-----------------------< The question is not "What is the answer?"; rather, | the question is "What is the question?" --Poincare | ===================================================' From colket@colket.org Thu Feb 19 15:52:25 1998 Return-Path: Received: from cs.ida.org by cronus.csed.ida.org (SMI-8.6/SMI-SVR4) id PAA06898; Thu, 19 Feb 1998 15:52:25 -0500 Received: from mail.acm.org (mail.acm.org [199.222.69.4]) by cs.ida.org (8.8.7/8.8.7) with ESMTP id PAA20007 for ; Thu, 19 Feb 1998 15:53:34 -0500 (EST) Received: from sw-eng.falls-church.va.us (ns1.sw-eng.falls-church.va.us [199.75.54.2]) by mail.acm.org (8.8.5/8.7.5) with ESMTP id PAA49394; Thu, 19 Feb 1998 15:52:01 -0500 Received: from smtp2.erols.com by sw-eng.falls-church.va.us (8.8.8/) id UAA16953; Thu, 19 Feb 1998 20:48:36 GMT Received: from default (207-172-69-78.s269.tnt14.brd.erols.com [207.172.69.78]) by smtp2.erols.com (8.8.8/8.8.5) with SMTP id PAA26822; Thu, 19 Feb 1998 15:50:53 -0500 (EST) Message-ID: <34EC9A7A.7262@colket.org> Date: Thu, 19 Feb 1998 15:47:54 -0500 From: Currie Colket Reply-To: colket@colket.org X-Mailer: Mozilla 3.01C-KIT (Win95; I) MIME-Version: 1.0 To: "C. Daniel Cooper" CC: ASIS-officers@sw-eng.falls-church.va.us, tom@xavier.ds.boeing.com, stan@forge.ds.boeing.com, maretta@longshot.ds.boeing.com, bobl@longshot.ds.boeing.com Subject: Re: ASIS ease of use References: <199802190009.QAA20009@longshot.ds.boeing.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 5925 Status: OR Dan, > > Great! This will probably be the outcome, pending negative comments. By > > the way, Sergey has generated the following extensions: > > > > function Is_Dispatching_Call (Call : Asis.Element) > > return Boolean; > > function Is_Dispatching_Operation (Declaration : Asis.Element) > > return Boolean; > > function Acts_As_Spec (Declaration : Asis.Element) > > return Boolean; > > function Is_Renaming_As_Body (Declaration : Asis.Element) > > return Boolean; > > function Components (E : Asis.Element) > > return Asis.Element_List; > > > > Presumeably we might want to include Is_Dispatching_Operation as well? > > Thoughts? > > Actually, I like *all* of the above. Acts_As_Spec, Is_Renaming_As_Body, and Components appear to me more in keeping with the concept of secondary interfaces. It would be hard to justify having these as primary interfaces. Yes? > > Depending on the issues raised for the ASIS Final CD Ballot, we may need > > a meeting for their resolution. I am currently anticipating we can > > resolve all the issues via email. Perhaps we might want to consider a > > meeting in early April dedicated to resolving issues and taking the > > first step towards identifying secondary queries. If most of the ASIS > > Final CD Ballot issues become resolved before the meeting then the > > meeting can devote its entirity to the secondary queries. > > Like last year, I'll be available March 21-29; maybe DDC-I (Joyce Tokar) > would like to host us again :-) Is this your spring break? There are 3 potential problems => 1. We might not have the official ballot comments from SC22 by 21 March. I expect we will get the balloting results by 16 March and the comments by 25 March. I would feel better about such a near term date selection if we had the SC22 balloting comments in hand. 2. Efforts at this time really need to focus on the comment resolution activity. 3. This could be fast turnaround for travel approval for many folks. Clyde Roby has volunteered to host the next meeting at IDA. What is your next window of opportunity? > > Otherwise, I fear ASIS will only see light > > in (many fewer) development groups, who have made a large investment > > in building Ada tools. Without a useful set of tool-oriented higher- > > level queries, I see the broader, casual, lightweight use of ASIS > > never really materializing, relegating ASIS to an arcane specialty. > > To underscore the above concern, here's a comment from Dan Ehrenfried: > > : As a note, in the years that Rational offered the LRM_interfaces, > : I can remember less that 5 customers who seriously tried to do this > : kind of analysis. Rational technical people did most of this kind of > : customization programming. So the interfaces were used in this way, > : but not by the general populace. > > I don't think ASIS must necessarily suffer the same fate; but we still > have some way to go, to make ASIS sufficiently easy to use for ordinary > engineers. > > > Incidently, Dan has been pushing me on this issue for a long time. I > > wanted to keep the focus on the ASIS specification. The ASIS > > specification is practically in auto drive so it is time to address the > > secondary queries. The fact that ASIS for GNAT already has identified 5 > > secondary queries indicates that this is an important area to focus. > > I have been asking our engineers who try ASIS to keep a list of features > they expected but that are missing. So far, most are along the lines of: > multiple ways of outputting names (fully qualified or not, capitalized > or not, uniqueness markers for overloaded names, etc) and other string > management utilities; a higher-level "framework" for canonical traversal > (I believe Bill Thomas is working on an example of this); iterators and > list management utilities; etc. > > Interestingly, another major area for improvement does not require new > secondary queries at all, but rather involves better/more user-oriented > examples/documentation/tutorials. For example, one user I talked to had > complaints about the tedium of locating the context after landing on a > specific element of interest -- a bottom-up approach; later, he realized > he could simply cache this in passing, as the traversal zeroed in on the > element. The implicit top-down nature of the traversal had simply eluded > him in the Appendix B examples he had started from. > > And even expert users can experience surprises: we had a recent case > where Dan Ehrenfried's Ada Analyzer did not recognize T'First to be the > same thing as T'first (ie, case sensitivity). Gary Barnes responded: > > : To make a long story short, Diana uppercases everything so the two forms > : should be equivalent. The ASIS program can make calls either to read the > : Diana (correct) or to read the text image of the attribute (incorrect). > : Ada Analyzer should do the former but it appears to be doing the latter. > > ...and indeed, it turned out that the tool was working from the text > image (which was capitalized inconsistently) rather than using the > attribute designator name. Good user manuals should go a long way > towards helping *all* users succeed with ASIS. These are all excellent thoughts. Perhaps you can put together a strawman that can be used to guide the discussion at the next meeting? The strawman possibly could have categories of useful interfaces as well as desired tutorial, documentation, and examples. We could bounce the strawman off asis-technical for additional thoughts. You might even want to consider publishing such a strawman in Ada Letters. The next deadline of 28 February would have the strawman published in the May/June issue, practical if our next meeting would be held in mid May or June. We would submit it as a ASISWG report to preclude the queue for papers. v/r Currie and Clyde From cooper@longshot.ds.boeing.com Thu Feb 19 19:11:32 1998 Return-Path: Received: from cs.ida.org by cronus.csed.ida.org (SMI-8.6/SMI-SVR4) id TAA07068; Thu, 19 Feb 1998 19:11:32 -0500 Received: from mailgate2.boeing.com (mailgate2.boeing.com [199.238.248.100]) by cs.ida.org (8.8.7/8.8.7) with ESMTP id TAA25885 for ; Thu, 19 Feb 1998 19:12:45 -0500 (EST) Received: from splinter.boeing.com ([130.42.28.12]) by mailgate2.boeing.com (8.8.5/8.8.5) with ESMTP id QAA26476; Thu, 19 Feb 1998 16:12:10 -0800 (PST) Received: from longshot.ds.boeing.com by splinter.boeing.com with ESMTP (1.37.109.16/16.2) id AA107623530; Thu, 19 Feb 1998 16:12:10 -0800 Received: by longshot.ds.boeing.com (SMI-8.6/SMI-SVR4) id QAA20698; Thu, 19 Feb 1998 16:12:07 -0800 Date: Thu, 19 Feb 1998 16:12:07 -0800 From: cooper@longshot.ds.boeing.com (C. Daniel Cooper) Message-Id: <199802200012.QAA20698@longshot.ds.boeing.com> To: colket@colket.org Subject: Re: ASIS ease of use Cc: tom@xavier.ds.boeing.com, Roby@ida.org X-Sun-Charset: US-ASCII Content-Length: 3170 Status: OR Currie, > Date: Thu, 19 Feb 1998 15:47:54 -0500 > From: Currie Colket > To: "C. Daniel Cooper" > CC: ASIS-officers@sw-eng.falls-church.va.us, tom@xavier.ds.boeing.com, > stan@forge.ds.boeing.com, maretta@longshot.ds.boeing.com, > bobl@longshot.ds.boeing.com Did you manually append ".ds.boeing.com" to some of the addressees above? We've had trouble where our out-going mailer failed to do that, resulting in bounce-backs to you when you reply. > Acts_As_Spec, Is_Renaming_As_Body, and Components appear to me more in > keeping with the concept of secondary interfaces. It would be hard to > justify having these as primary interfaces. Yes? Yes, I agree. I'm just looking to maximize usability :-) > > Like last year, I'll be available March 21-29; maybe DDC-I (Joyce Tokar) > > would like to host us again :-) > > Is this your spring break? Yes > What is your next window of opportunity? mid-June through September. > These are all excellent thoughts. Perhaps you can put together a > strawman that can be used to guide the discussion at the next meeting? I figured you'd ask that. The answer depends on a couple of things: 1) management support for the time to do this; and 2) how much input we may or may not have collected by then (from our ASIS users). > The strawman possibly could have categories of useful interfaces as well > as desired tutorial, documentation, and examples. We could bounce the > strawman off asis-technical for additional thoughts. We might be able to start with something high-level like that; but fleshing it out will require contributions from many parties... unless somebody like Dan Ehrenfried/Rational would want to volunteer a lot of proprietary work. Another consideration (that has already been pointed out) is that since secondary queries are by definition built on the primary ASIS queries, then their implementations would likely *not* be proprietary but rather public domain; ie, they aren't vendor dependent (unlike the primary queries), such that no vendor would invest in or sell them; nor would they need to be "standard". The same would probably be true of the documentation, etc. So, what we're talking about here is an ASISWG volunteer effort to produce a public domain set of user-oriented, high-level utilities with the accompanying tutorials/documentation/examples. Maybe this effort could be supported through GNAT, or maybe include ATIP funding? I defer to your expertise here: this is the non-technical part of the problem, and is the reason that I keep poking at you about it. How can we make this happen? Consequent to that, we can then address the technical issues. Do you have any encouragment? -- C. Daniel Cooper ==========v=======================. Adv Computing Technologist | All opinions are mine | 206-655-3519 | and may not represent | CDaniel.Cooper@Boeing.com | those of my employer. | ---------------------------^-----------------------< The question is not "What is the answer?"; rather, | the question is "What is the question?" --Poincare | ===================================================' From colket@colket.org Fri Feb 20 11:43:16 1998 Return-Path: Received: from cs.ida.org by cronus.csed.ida.org (SMI-8.6/SMI-SVR4) id LAA08817; Fri, 20 Feb 1998 11:43:16 -0500 Received: from smtp2.erols.com (smtp2.erols.com [207.172.3.235]) by cs.ida.org (8.8.7/8.8.7) with ESMTP id LAA13891 for ; Fri, 20 Feb 1998 11:44:31 -0500 (EST) Received: from default (207-172-41-40.s40.tnt14.brd.erols.com [207.172.41.40]) by smtp2.erols.com (8.8.8/8.8.5) with SMTP id LAA24127; Fri, 20 Feb 1998 11:44:19 -0500 (EST) Message-ID: <34EDB22F.2AA@colket.org> Date: Fri, 20 Feb 1998 11:41:19 -0500 From: Currie Colket Reply-To: colket@colket.org X-Mailer: Mozilla 3.01C-KIT (Win95; I) MIME-Version: 1.0 To: "C. Daniel Cooper" CC: tom@xavier.ds.boeing.com, Roby@ida.org Subject: Re: ASIS ease of use References: <199802200012.QAA20698@longshot.ds.boeing.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 4493 Status: OR Dan, > Did you manually append ".ds.boeing.com" to some of the addressees > above? We've had trouble where our out-going mailer failed to do that, > resulting in bounce-backs to you when you reply. Yes - I got a bounce back on a previous message. You should get your mailer fixed. > > Acts_As_Spec, Is_Renaming_As_Body, and Components appear to me more in > > keeping with the concept of secondary interfaces. It would be hard to > > justify having these as primary interfaces. Yes? > > Yes, I agree. I'm just looking to maximize usability :-) > > > > Like last year, I'll be available March 21-29; maybe DDC-I (Joyce Tokar) > > > would like to host us again :-) > > > > Is this your spring break? > > Yes > > > What is your next window of opportunity? > > mid-June through September. > > > These are all excellent thoughts. Perhaps you can put together a > > strawman that can be used to guide the discussion at the next meeting? > > I figured you'd ask that. The answer depends on a couple of things: > 1) management support for the time to do this; and 2) how much input > we may or may not have collected by then (from our ASIS users). > > > The strawman possibly could have categories of useful interfaces as well > > as desired tutorial, documentation, and examples. We could bounce the > > strawman off asis-technical for additional thoughts. > > We might be able to start with something high-level like that; but > fleshing it out will require contributions from many parties... > unless somebody like Dan Ehrenfried/Rational would want to volunteer > a lot of proprietary work. Another consideration (that has already > been pointed out) is that since secondary queries are by definition > built on the primary ASIS queries, then their implementations would > likely *not* be proprietary but rather public domain; ie, they aren't > vendor dependent (unlike the primary queries), such that no vendor > would invest in or sell them; nor would they need to be "standard". They could easily be public domain or lisenced under the GPL with public releases. There are advantages under both schemes. I think the availability of artifacts under the ASIS Home Page is a preferred way to do things. > The same would probably be true of the documentation, etc. So, what > we're talking about here is an ASISWG volunteer effort to produce a > public domain set of user-oriented, high-level utilities with the > accompanying tutorials/documentation/examples. Maybe this effort > could be supported through GNAT, or maybe include ATIP funding? Volunteer effort is the method the ASIS interfaces were developed in the first place. I think this is a very good model. Perhaps there is good cause to promote strong participation from the other volunteer groups, such as OOWG for Object Oriented issues/examples and the SAFEWG for safety and integrity issues and examples. If we were to use GNAT support, this might alienate Aonics, DDC-I, and Rational. ATIP funding will no longer be available. There are other activities ow which we might be able to leverage. The principle effort will be that of volunteers. > I defer to your expertise here: this is the non-technical part of > the problem, and is the reason that I keep poking at you about it. > How can we make this happen? Consequent to that, we can then address > the technical issues. Do you have any encouragment? The best way is to entice interest. As I suggested in the previous email, having a 1-2 page strawman in Ada Letters which identifies potential approaches should stir up interest. The timing could be excellent. We should have the hopefully positive ballot for the CD Final ballot. We should have the fully implemented ASIS for GNAT for 3.11a (Last night Robert Dewar indicated that this release would be available within the next couple of weeks along with a new tool based on ASIS which eliminates dead subprograms within the context. [FYI, the latest public release of ASIS for GNAT is version 3.09 yet the latest public release of GNAT is 3.10 - This should be corrected soon with the release of 3.11a]) The strawman should identify proposed high-level categories for the high-level secondary interfaces. With such a list, it would be possible to confront related organizations (e.g., OOWG, SAFEWG) and more effectively solicit interest and input. Again, this has a short fuse as it is needed by 28 February. Actually KM George can slip a week if we can tell him how many pages we will require. v/r Currie From roby Fri Feb 20 15:23:59 1998 Return-Path: Received: by cronus.csed.ida.org (SMI-8.6/SMI-SVR4) id PAA09391; Fri, 20 Feb 1998 15:23:58 -0500 From: roby (Clyde Roby) Message-Id: <199802202023.PAA09391@cronus.csed.ida.org> Subject: Provide additional descriptions for Ada context and operations on elements To: ASIS-Comment@SW-Eng.Falls-Church.Va.US (ASIS-Comment) Date: Fri, 20 Feb 1998 15:23:58 -0500 (EST) Cc: Cooper@Boeing.Com (Dan Cooper), roby (Clyde Roby), Colket@ACM.Org (Currie Colket) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 583 Status: OR !ASIS Issue !topic Provide additional descriptions for context and operations on elements !reference ASIS 95-2.2 !from Dan Cooper !keywords context environment operations elements !discussion Clause 2.2 (ASIS queries) should have additional descriptions for context and operations on elements. The following additional figures and descriptive text should be provided: relationship between the Ada environment and the ASIS context, compilation unit from a black box perspective, compilation unit from a white box perspective, and a figure depicting the operations on an element. From colket@colket.org Sun May 10 21:44:37 1998 Return-Path: Received: from cs.ida.org by cronus.csed.ida.org (SMI-8.6/SMI-SVR4) id VAA03317; Sun, 10 May 1998 21:44:37 -0400 Received: from smtp2.erols.com (smtp2.erols.com [207.172.3.235]) by cs.ida.org (8.8.7/8.8.7) with ESMTP id VAA18578 for ; Sun, 10 May 1998 21:45:58 -0400 (EDT) Received: from colket.org (207-172-41-159.s159.tnt10.brd.erols.com [207.172.41.159]) by smtp2.erols.com (8.8.8/8.8.5) with ESMTP id VAA24382; Sun, 10 May 1998 21:45:56 -0400 (EDT) Message-ID: <3556583F.C65630C9@colket.org> Date: Sun, 10 May 1998 21:45:35 -0400 From: Currie Colket Reply-To: colket@colket.org X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: ASIS Technical CC: Clyde Roby , Clyde Roby Subject: Issue #090 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1371 Status: OR Dear asis-technical, Attached is Issue #090 with a proposed resolution of ACCEPT and the proposed solution. The solution was developed with the originator. This solution will be made part of the ASIS DIS if there are no negative comments addressed to asis-technical by 15 May. Please send concerns to the asis-technical mailing list with Issue #090 in the subject line. v/r Currie Colket !ASIS Issue #090 !topic Provide additional descriptions for context and operations on elements !reference ASIS 95-2.2 !from Dan Cooper !keywords context environment operations elements !discussion Clause 2.2 (ASIS queries) should have additional descriptions for context and operations on elements. The following additional figures and descriptive text should be provided: relationship between the Ada environment and the ASIS context, compilation unit from a black box perspective, compilation unit from a white box perspective, and a figure depicting the operations on an element. !resolution Accept, with Modification. !date 98-05-06 !Notes Additional descriptions and text were added to 2.2.1, Structural queries, to explain a compilation unit from both a black box and a white box perspective. Additional figures were provided in section 2: Figure 2, ASIS as interface to Ada compilation environment; Figure 3, ASIS Context; and Figure 5, Operations on elements. From roby Thu May 21 12:59:09 1998 Return-Path: Received: by cronus.csed.ida.org (SMI-8.6/SMI-SVR4) id MAA12603; Thu, 21 May 1998 12:59:08 -0400 Date: Thu, 21 May 1998 12:59:08 -0400 From: roby (Clyde Roby) Message-Id: <199805211659.MAA12603@cronus.csed.ida.org> To: Colket@ACM.Org Cc: croby Subject: issue090.i Content-Length: 1061 Status: OR !ASIS Issue #090 !topic Provide additional descriptions for context and operations on elements !reference ASIS 95-2.2 !from Dan Cooper !keywords context environment operations elements !discussion Clause 2.2 (ASIS queries) should have additional descriptions for context and operations on elements. The following additional figures and descriptive text should be provided: relationship between the Ada environment and the ASIS context, compilation unit from a black box perspective, compilation unit from a white box perspective, and a figure depicting the operations on an element. !resolution Accept, with Modification. !date 98-05-21 !Notes Additional descriptions and text were added to 2.2.1, Structural queries, to explain a compilation unit from both a black box and a white box perspective. Additional figures were provided in section 2: Figure 2, ASIS as interface to Ada compilation environment; Figure 3, ASIS Context; and Figure 5, Operations on elements. A new section 2.4.3 "Notional ASIS Application" was added to support this comment.