Return-Path: Delivered-To: apmail-jakarta-oro-dev-archive@apache.org Received: (qmail 31929 invoked from network); 30 Jan 2002 10:09:11 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 30 Jan 2002 10:09:11 -0000 Received: (qmail 11996 invoked by uid 97); 30 Jan 2002 10:09:20 -0000 Delivered-To: qmlist-jakarta-archive-oro-dev@jakarta.apache.org Received: (qmail 11939 invoked by uid 97); 30 Jan 2002 10:09:19 -0000 Mailing-List: contact oro-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "ORO Developers List" Reply-To: "ORO Developers List" Delivered-To: mailing list oro-dev@jakarta.apache.org Received: (qmail 11928 invoked from network); 30 Jan 2002 10:09:19 -0000 Message-Id: <200201301012.g0UAC5r02694@yoda.savarese.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "ORO Developers List" Subject: Re: special control characters In-reply-to: Your message of "Wed, 30 Jan 2002 09:23:12 GMT." <3C57BB80.67AF41B9@Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Jan 2002 05:12:05 -0500 From: "Daniel F. Savarese" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N In message <3C57BB80.67AF41B9@Sun.COM>, Michael Davey - Sun UK Support Engineer writes: >Okay, I think that what you are saying (reading between the lines) is >that >the substitution and replacement strings are parsed, but the input that >we search on is not parsed. I see now that I never understood the original question. I didn't look at your example closely enough to see that you were using "\\a\\b..." in your input. >If this is the case, would it make sense to add a parser for the input >string? I don't think so because the objective is to search for patterns in Java strings, not Perl strings. You can always create your own input filter for your special purpose. daniel -- To unsubscribe, e-mail: For additional commands, e-mail: