From jj@ddci.dk Mon Feb 10 04:02:13 1997
Return-Path: <croby@sw-eng.falls-church.va.us>
Received: from ida.org by cronus.csed.ida.org (SMI-8.6/SMI-SVR4)
	id EAA01903; Mon, 10 Feb 1997 04:02:12 -0500
Received: from sw-eng.falls-church.va.us (ns1.sw-eng.falls-church.va.us) by ida.org (4.1/SMI-4.1)
	id AA24792; Mon, 10 Feb 97 04:02:39 EST
Received: from uucp.DK.net by sw-eng.falls-church.va.us (8.7.1/)
	id IAA00196; Mon, 10 Feb 1997 08:56:34 GMT
Received: from ddci (uucp@localhost) by uucp.DK.net (8.6.12/8.6.12) with UUCP id JAA27967; Mon, 10 Feb 1997 09:59:07 +0100
Received: from sparc7.ddci.dk by ddci.dk (4.1/j1.1.2)
	id AA18356; Mon, 10 Feb 97 09:34:52 +0100
Date: Mon, 10 Feb 97 09:34:52 +0100
Message-Id: <9702100834.AA18356@ddci.dk>
Received: by sparc7.ddci.dk (4.1/SMI-4.1)
	id AA24754; Mon, 10 Feb 97 09:33:34 +0100
From: Jesper Joergensen <jj@ddci.dk>
To: asis-comment@sw-eng.falls-church.va.us
Cc: colket@smtp-gw.spawar.navy.mil
Subject: Various comments
Content-Length: 5333
Status: OR

!topic Corresponding_Declaration
!reference ASIS 95-15.26(?)
!from Jesper Jorgensen 97-02-09
!discussion
 
I miss to see the usefuleness of being able to locate a declaration in another
context. How should the body and declaration be related?. If there is a
compilation unit body X in some context and a compilation unit specification X
in some other context, they might be totally unrelated, just accidentally
having the same name. If they are unrelated, how should ASIS be able to locate
some inner unit?
 
I think that only searching in the same context makes sense. What is the
intended use of the other possibility?