Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 59254 invoked from network); 16 Jul 2002 17:45:42 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 16 Jul 2002 17:45:41 -0000 Received: (qmail 1038 invoked by uid 97); 16 Jul 2002 17:45:54 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 1022 invoked by uid 97); 16 Jul 2002 17:45:54 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 1010 invoked by uid 98); 16 Jul 2002 17:45:53 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <009401c22cf1$38e88c20$f86e78d5@oemcomputer> From: "Stephen Colebourne" To: "Jakarta Commons Developers List" , "Ola Berg" References: Subject: Re: [PROPOSAL] char iteration Date: Tue, 16 Jul 2002 18:50:03 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Can you point us at a link with the code, or javadoc for a little more info. I haven't quite 'got it' yet. Stephen ----- Original Message ----- From: "Ola Berg" To: Sent: Tuesday, July 16, 2002 12:29 PM Subject: [PROPOSAL] char iteration > In several of my projects, there is a common interface called CharIterator (in process of rework, I think CharStream is a better name). I have it in my io-classes, in my config framework, in my template engine, but firstmost I have it in my parser framework (a system for building fast and lightweight parsers using the State pattern and building parsing state machines). > > I would like to donate the parser framework, as I think that it would fit as a jakarta-API, but I think that: > > a) the char iteration mechanism should be provided separately and merged with similar efforts, as it is better to have _one_ single notion of a serial view on character (and byte) sequences in _all_ jakarta projects. > > b) The concept is low-level and useful in disparate areas, so it should be taken in consideration as a candidate member of the core family of commons packages, or having the interface published in some interfaces/patterns package. > > What do you think? Is char iteration something for commons-core to deal with (I think it is)? Can we merge the different jakarta solutions on char (and possibly byte) iteration into one fruitful concept? > > And a separate and less important question: would a parser helper framework fit? I think it might, as text parsing is a common task, but I don\'t want to donate something that would lead to more confusion or less interoperability between the existing jakarta components. > > /O > > -------------------- > ola.berg@arkitema.se > 0733 - 99 99 17 > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > -- To unsubscribe, e-mail: For additional commands, e-mail: