Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of flamefew@gmail.com designates
 209.85.128.191 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=IW4TpOha2f051zhWpgOqtHiCz+4jDUSihE4ySIYFkTu4FKWg/IaCZUF3tHy3+N5l/Wix83GEV2AbbRaCnuWVObVwYtPChlwq0545UldHsPgeh9RrCdQDhLDtbDY3GwgA1K7Rrw1R6uIck6qZTeqiHWZj/FO/Hx7sRtgOh298PdE=
Message-ID: <31cc37360710252239i1c3683c6pf28014053ef74890@mail.gmail.com>
Date: Thu, 25 Oct 2007 22:39:16 -0700
From: "Henri Yandell" <flamefew@gmail.com>
To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Subject: Re: TextIterable ?
In-Reply-To: <ca53c8f80710251940rb1d5897j78da194a24fc5435@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <ca53c8f80710250852o1c98e44cy7175163f8f25d8bf@mail.gmail.com>
	 <31cc37360710251919i46e69dc1pba41dd75f2ebf9e2@mail.gmail.com>
	 <ca53c8f80710251940rb1d5897j78da194a24fc5435@mail.gmail.com>

On 10/25/07, Hanson Char <hanson.char@gmail.com> wrote:
> Henri,
>
> LineIterator is intended/designed to be a hidden implementation behind
> TextIterable.  It's like putting the cart in front of the horse.
> Things don't make much sense if LineIterator is taken out of context
> as a standalone public class - issues of InputStream vs Reader,
> encoding, closing of input stream, etc. go away at the higher level of
> abstraction, aka TextIterable.

My personal view is that:

a) I hate APIs that force me to think in terms of File/URL and not in
term of streams. It's like not having piping in unix.
b) The class that opens the stream should close the stream.

> The 1.5 issue is, unfortunate, a real issue.  I haven't programmed in
> pre-1.5 Java for 2+ years now.  Sorry for the folks who are not so
> lucky.

Yeah, it's a pain in the arse and more; the inability to move the
libraries to 1.5 slowly kills Commons. Thus you see various
Collections clones out there starting up with a 1.5 focus. A lot of
that though is because Collections -> 1.5 isn't something that you
just wave a magic wand on.

Personally I finally moved to 1.5 in the last year. 1.4 is yesterday's
trash to me now. As a whole Commons is just about at the point of
being happy to drop 1.3 support, with new components being 1.5+.

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org