ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Murdoch" <>
Subject RE: [VOTE] Promotion of FilterReaders proposal to main development tree.
Date Thu, 28 Feb 2002 07:34:54 GMT

> -----Original Message-----
> From: Magesh Umasankar []
> Sent: Thursday, 28 February 2002 12:06 PM
> To: Ant Developers List
> Subject: [VOTE] Promotion of FilterReaders proposal to main development
> tree.
> Hi,
> I would like to call upon a vote for the promotion of
> the FilterReaders proposal from the sandbox to the main
> development tree.

+1 - very cool.

I have some tiny nitpicks, however:

* Can you split up ChainReaderHelper.processStream() into two methods:  A
method that assembles the Reader, and a utility method turns a Reader into a
String (this method would fit better on FileUtils).  You also might want to
use a StringBuffer when you're doing the conversion.

Reason for splitting the method, is that if we are going to be using the
filters in <copy> and <move>, we don't want to be building the file into a
String in-memory, we just want to stream it through.  That means we'll need
a Reader.

* Why does LoadProperties parse the properties?  Why not use

* Should BaseFilterReader.skip() be using rather than

* You might want to look at refactoring some of the common(-ish) stuff from
the filters down into BaseFilterReader.  For example, nearly all of the
filters deal with lines of text, and each has their own 'read a line from
the file' code.  It would be better if BaseFilterReader (or an intermediate
LineFilterReader class) took care of this for the filters.  Same with
setParameters(), setInitialised(), getInitialised(), etc.  And dealing with

* Any chance of a filter that adjusts end-of-line characters?  How about a
regexp version of LineContains?


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message