Agreed.... thats why I'm bringing this up.
But if we let <tstamp> change properties, then why not <available> and
<condition>?
If we let everything change properties then we might as all be writing our
build scripts in Perl! :)
Property immutability is what makes Ant powerful - I'm just not sure where
to draw the line. And apparently this isn't a black & white issue.
Erik
----- Original Message -----
From: "Bruce Atherton" <[EMAIL PROTECTED]>
To: "Ant Developers List" <[EMAIL PROTECTED]>
Cc: "Erik Hatcher" <[EMAIL PROTECTED]>
Sent: Monday, November 26, 2001 9:32 PM
Subject: Re: <available> / <condition> breaking immutability
> At 08:41 PM 11/26/2001 -0500, you wrote:
> >Here are some things within Ant's core that rely on property mutability:
> >
> > <tstamp>
>
> I'm not sure this is what you are proposing, but if you change <tstamp> so
> that DSTAMP and TSTAMP become immutable, you will lose what I consider a
> very valuable ability. Right now, you can find out how long each section
of
> your build takes, which can be very valuable information. It let's you
make
> optimizations more effectively, for example.
>
> What I am talking about is something like this:
>
> <target name="build" depends="init,checkout,compile />
>
> <target name="init" >
> <tstamp />
> <echo message="Started Build - ${DSTAMP} ${TSTAMP}" />
> </target>
>
> <target name="checkout" depends="init,do-checkout">
> <tstamp />
> <echo message="Finished Checkout - ${DSTAMP} ${TSTAMP}" />
> </target>
>
> <target name="compile" depends="init,do-compile">
> <tstamp />
> <echo message="Finished Compile - ${DSTAMP} ${TSTAMP}" />
> </target>
>
> Well, you get the idea. This is quite useful information to have and I'd
> hate to see it go just because you are chasing after the hobgoblin of
> consistency.
>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
