Description joerg 2010-08-18 02:33:51 EDT

Build Identifier: M20090917-0800

Obviously support for SearchPattern.R_REGEXP_MATCH is not implemented. Yet, the documentation of SearchPatter.createPattern(String stringPattern, int searchFor, int limitTo, int matchRule) does not mention it. Worse, createPattern() does not return null, but treats the regular expression as a normal pattern which leads to very unexpected behaviour.

The JavaDoc of SearchPattern.validateMatchRule(String stringPattern, int matchRule) says: "when the R_REGEXP_MATCH flag is set, then the pattern is rejected as this kind of match is not supported yet and-1 is returned". This is not the way it is implemented. This is very confusing as well.

I am not requesting that this feature be implemented (even thought that would be nice), but a hint in the API that R_REGEXP_MATCH is not ready for use would have saved me some hours.

Reproducible: Always

Steps to Reproduce:
1. Create a file Test.java:
class Test {
 private void a(){
   Object o = new Object();
   String s = o.toString();
 }
}
2. In your search implementation:
String regex = "java\\.lang\\.((String)|(Object));
SearchPattern pattern = SearchPattern.createPattern(regex,
IJavaSearchConstants.REFERENCES,IJavaSearchConstants.TYPE,
SearchPattern.R_REGEXP_MATCH);
...
SearchEngine se = new SearchEngine();
se.search(pattern, ..., ...,  ..., null);

you will notice that the respective SearchRequestor is never called.