Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-dev@jakarta.apache.org
To: ant-dev@jakarta.apache.org
Subject: Re: [Patch] Target attribute property expansion
References: <000901c10472$8bef6770$d900a8c0@viquity.com>
	<m3elrwx0s8.fsf@bodewig.bost.de>
	<01070516483201.02692@helm.realityforge.org>
From: Stefan Bodewig <bodewig@apache.org>
Date: 05 Jul 2001 10:24:51 +0200
In-Reply-To: Peter Donald's message of "Thu, 5 Jul 2001 16:48:32 +1000"
Message-ID: <m3ith7hjfw.fsf@bodewig.bost.de>
Lines: 29
User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Cuyahoga Valley)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Thu, 5 Jul 2001, Peter Donald <donaldp@apache.org> wrote:

> I actually think that we should do lazy evaluation of the DAG. ie
> only look up next element in DAG as we "get" to it.

Could you please explain how this should work?  I'm not sure I know
what you mean by "look up" and "get to" in this context.

> This is for two reasons mainly;

You mention three 8-)

> 1. Support crazy self-modifying projects like Jose wanted

He did?

> 2. Not force the loading of all project files at startup

If we allow targets in the main file to depend on targets in other
files, we'll have to load and parse this other file anyway, don't we?

> 3. Cutdown on redundent scanning at start that is not needed and
> costly in large projects

Scanning for what?  If you are talking about not searching for cycles
in the dependency graph that we are never going to touch, that is fine
with me.

Stefan