Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <ant-dev@jakarta.apache.org>
To: ant-dev@jakarta.apache.org
Subject: Re: Name collisions
References: <000f01c1c313$b3a933d0$0100a8c0@jose>
From: Stefan Bodewig <bodewig@apache.org>
Date: 04 Mar 2002 12:21:07 +0100
In-Reply-To: <000f01c1c313$b3a933d0$0100a8c0@jose>
Message-ID: <m3ofi4wpcs.fsf@bodewig.bost.de>
Lines: 32
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Civil Service)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Mon, 4 Mar 2002, Jose Alberto Fernandez <j_a_fernandez@yahoo.com>
wrote:

> As far as I can see in the current ANT1 code, there seems to be no
> provisions on what happens if I define a task and a datatype using
> the same name. The definer tasks do not check across different
> namespaces.

This is true.

> To make clear what is the situation I am referring to let me
> formalize it:
> 
>     - Given two roles, A & B, triggered by the same container
>     interface (e.g., task and data-type) and given that a particular
>     element name, N, is registered in role A, what should be the
>     correct behaviour when one attempts to register N in B.

I'm not sure what triggered by the same container interface means
here.

In the case of tasks and data-type we only have a disambiguity because
both can be defined within the same container elements (target for
example), is this the "triggered by the same container interface" you
are talking about?

If you want to generalize this to arbitrary roles, you cannot do
anything at all, as you cannot know whether there is a context in
which roles A and B both can be used at the same time, at least not at
the point where things get registered.  Or can you?

Stefan

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>