Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(176)

Issue 13784: * Fixed bug in handling of quantified look-aheads. (Closed)

Created:
12 years ago by Lasse Reichstein
Modified:
9 years, 6 months ago
CC:
v8-dev
Visibility:
Public.

Description

Quantified look-aheads are sometimes removed entirely, leaving only a single atom node. A flag was not set in this case, leading the wrapper code to think the pattern was equal to the atom and use the pattern in the indexOf operation.

Patch Set 1 #

Total comments: 3
Unified diffs Side-by-side diffs Delta from patch set Stats (+61 lines, -59 lines) Patch
M src/jsregexp.h View 1 chunk +2 lines, -2 lines 0 comments Download
M src/jsregexp.cc View 1 chunk +4 lines, -2 lines 0 comments Download
M src/parser.cc View 7 chunks +10 lines, -10 lines 3 comments Download
M test/cctest/test-regexp.cc View 3 chunks +45 lines, -45 lines 0 comments Download

Messages

Total messages: 2 (0 generated)
Lasse Reichstein
Small code review
12 years ago (2008-12-12 09:45:36 UTC) #1
Christian Plesner Hansen
12 years ago (2008-12-12 09:52:01 UTC) #2
Lgtm

http://codereview.chromium.org/13784/diff/1/4
File src/parser.cc (right):

http://codereview.chromium.org/13784/diff/1/4#newcode530
Line 530: bool IsNonSimple();
You should generally avoid negative method names.  How about IsSimple()?

http://codereview.chromium.org/13784/diff/1/4#newcode551
Line 551: bool non_simple_;
Ditto.

http://codereview.chromium.org/13784/diff/1/4#newcode3555
Line 3555: bool RegExpParser::IsNonSimple() {
This should be a simple accessor, not a full camel case method.

Powered by Google App Engine
This is Rietveld 408576698