Not that anybody is unaware, but...
A lot of Ant targets are constructed to transform
data from one form to another, and tend to use
temporary files as the medium, which is not so
attractive.
To highlight this point, the example below is
creating curtag.txt and rewriting its contents
and later deleting it when, ideally, all this
can be performed in memory (as stream transforms),
without messy intermediate files.
Seems like we have a nice use case for writing
a filterreader that works somewhat like <replaceregexp>
Cheers,
Magesh
****************************************************
* Doctor: A person who kills your ills by pills, *
* and then kills you with his bills. *
****************************************************
----- Original Message -----
From: "Stefan Bodewig" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 10, 2003 6:42 AM
Subject: Re: FilterChain is there a regexp?
> On Fri, 10 Jan 2003, Jose Alberto Fernandez
> <[EMAIL PROTECTED]> wrote:
>
> > I am not sure I understood, do <linecontainsregexp> and
> > <replaceregexp> already exists or are those just the names you are
> > proposing for them?
>
> They exist (<replaceregexp> is a(n optional) task, not a filter,
> though) in 1.5.
>
> <copy file="${basedir}/CVS/Tag" tofile="curtag.txt"/>
> <replaceregexp file="curtag.txt" match=".\(.*\)" replace="\1"/>
> <loadfile property="curbranch" srcFile="curtag.txt">
> <filterchain>
> <striplinebreaks/>
> </filterchain>
> </loadfile>
> <delete file="curtag.txt"/>
>
> is a way without sed, that is as silly as your original 8-)
>
> Stefan
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
