Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9198853
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 17, 20262026-06-17T22:23:12+00:00 2026-06-17T22:23:12+00:00

Possible Duplicate: String.replaceAll() anomaly with greedy quantifiers in regex I was writing code that

  • 0

Possible Duplicate:
String.replaceAll() anomaly with greedy quantifiers in regex

I was writing code that uses Matcher#replaceAll and found following result highly confusing:

Pattern.compile("(.*)").matcher("sample").replaceAll("$1abc");

Now, I would expect the output to be sampleabc but Java throws at me sampleabcabc.

Does anybody have any ideas why?

Now, sure, when I anchor the pattern (^(.*)$) the issue goes away. Still I don’t know why the hell would replaceAll do a double replacement like that.

And to add insult to injury, following code:

Pattern.compile("(.*)").matcher("sample").replaceFirst("$1abc")

works as expected, returning just sampleabc.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-17T22:23:13+00:00Added an answer on June 17, 2026 at 10:23 pm

    It looks like it’s matching the empty string at the end of the input, for some reason. (I can see why it would match; I’m intrigued that it matches once and only once.)

    If you change replaceAll("$1abc") to replaceAll("'$1'abc") the result is 'sample'abc''abc.

    Note that if you change (.*) to (.+) then it works correctly, because it has to match at least one character.

    The diagnosis is confirmed by this code:

    Matcher matcher = Pattern.compile("(.*)").matcher("sample");
    
    while (matcher.find()) {
        System.out.printf("%d to %d\r\n", 
                          matcher.start(), 
                          matcher.end());
    }
    

    … which outputs:

    0 to 6
    6 to 6
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Possible Duplicate: String.replaceAll() anomaly with greedy quantifiers in regex Strange behavior in regexes While
Possible Duplicate: java String.replaceAll without regex I have a string and I need to
Possible Duplicate: String, StringBuffer, and StringBuilder We know that String are immutable where StringBuffer
Possible Duplicate: String comparison in Objective-C I realize that the question is not very
Possible Duplicate: Resharper string.format shortcut In our large code base, unfortunately there are a
Possible Duplicate: String vs StringBuilder I just revisited some of the books that I
Possible Duplicate: String.Format exception when format string contains { Does following possible using C#
Possible Duplicate: Are string.Equals() and == operator really same? I know that in c#
Possible Duplicate: Java string comparison? I have encounter the following problem, I have an
Possible Duplicate: replace all occurrences in a string I found this question/answer: Use JavaScript

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.