public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "overholt at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/20504] New: java.util.regex implementation doesn't support quoting constructs Date: Wed, 16 Mar 2005 22:27:00 -0000 [thread overview] Message-ID: <20050316214802.20504.overholt@redhat.com> (raw) This was originally filed in GNU Classpath's BTS, but it should probably be here as well. Ziga Mahkovec wrote there (https://savannah.gnu.org/bugs/index.php?func=detailitem&item_id=12307): We were recently having some problems with the search functionality in native eclipse[1]. It boiled down to the lack of quoting regex constructs support in gnu.regexp.RE (\Q, \E). A simple test: Pattern.compile("\\Q" + "boo" + "\\E").matcher("Peekaboo").find(); returns false using classpath and true using java-sun. I'm attaching a more comprehensive Mauve test for the java.util.regex functionality. It consists of three test suites, adapted from PCRE[2] (which is BSD licensed): - testdata1: tests that are currently passed by classpath - testdata2: tests that currently fail (disabled since they probably need to be reviewed) - testdata3: tests that use quoting constructs I'm also attaching a tentative patch for the quoting constructs problem. [1] https://bugzilla.redhat.com/beta/show_bug.cgi?id=149927 [2] http://www.pcre.org/ -- Summary: java.util.regex implementation doesn't support quoting constructs Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: overholt at redhat dot com CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20504
next reply other threads:[~2005-03-16 21:48 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-16 22:27 overholt at redhat dot com [this message] 2005-03-17 0:01 ` [Bug libgcj/20504] " overholt at redhat dot com 2005-03-17 0:33 ` overholt at redhat dot com 2005-03-17 1:29 ` mckinlay at redhat dot com 2005-03-17 2:17 ` ziga dot mahkovec at klika dot si 2005-03-17 2:22 ` mckinlay at redhat dot com 2005-04-20 15:56 ` mckinlay at redhat dot com 2005-04-20 16:24 ` ziga dot mahkovec at klika dot si 2005-05-04 14:29 ` overholt at redhat dot com 2005-05-04 15:01 ` ziga dot mahkovec at klika dot si 2005-05-16 16:03 ` mark at gcc dot gnu dot org 2005-05-16 19:02 ` cvs-commit at gcc dot gnu dot org 2005-05-16 19:03 ` cvs-commit at gcc dot gnu dot org 2005-05-16 19:06 ` tromey at gcc dot gnu dot org 2005-05-16 19:18 ` ziga dot mahkovec at klika dot si
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20050316214802.20504.overholt@redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).